Cache mode query overview.

Hi guys,
In the Early Watch report I have an overview on how many queries use a certain cache mode (chapter 12.1), but it doesn't show which queries they are.
I have 4 queries with cache switched off and I'd like to know which ones they are. Any idea if there's a table/trx somewhere where I can find this information?
Thanks.
Eduard

hi Eduard,
yes, i added the info later just in case you want go by individual query, RSRT won't serve a mass checking.
please close the thread and reward helpful answer if RSRREPDIR serve your purpose.
hope this help.

Similar Messages

  • 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

  • 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....
    <b>Cache Mode:</b>
    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
    <b>Optimization Mode:</b>
    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.

  • Query read / cache modes are set in BW

    Hi Experts,
    What is query read / cache modes are set in BW in order to improve the query performance?
    Thanks
    Rohan

    Hi
    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.
    http://help.sap.com/saphelp_nw04/helpdata/en/57/b10022e849774f9961aa179e8763b6/content.htm
    Assign points if it helps...
    Regards,
    ARK

  • Distributed Cache Mode With W2k8 Enterprise ServerCore ???

    Hi, can someone teach me how to configure  BranchCache in Distributed Cache Mode with W2k8 Enterprise ServerCore? tks a lot!

    Hi,
    Since Server Core installation provides a minimal environment for running specific server roles, which reduces the maintenance and management requirements and the attack surface for those server
    roles, so the installation process of BranchCache Distributed Cache Mode is the same as the Windows Server 2008 with GUI. Since there isn’t any official document about this, I suggest we could use the following guides as reference.
    BranchCache Distributed Cache Mode Step by Step Guide
    http://www.microsoft.com/en-us/download/details.aspx?id=5772
    Here are some articles about how to configure a Server Core installation, they may be useful to us.
    Configuring a Server Core installation: Overview
    http://technet.microsoft.com/en-us/library/ee441257(v=ws.10).aspx
    Installing a server role on a server running a Server Core installation of Windows Server 2008: Overview
    http://technet.microsoft.com/en-us/library/ee441263(v=ws.10).aspx
    Installing Windows Features on a server running a Server Core installation of Windows Server 2008: Overview
    http://technet.microsoft.com/en-us/library/ee441259(v=ws.10).aspx
    If you face some issue during the configuration, please do not hesitate to let me know, I will be very happy to help.
    Best Regards,
    Andy Qi
    Andy Qi
    TechNet Community Support

  • Cache Mode 5 - BLOB/ Cluster Enhanced - Variables

    Hello,
    I have a very large query that I need to cache for performance.
    I'm using cache mode 5 - BLOB/Cluster Enhanced.
    I see that for variables in Char Restrictions area, it creates a new entry in RSRCACHE under my query under new Variables/Hierarchies section. But for variables in default values section it creates new selection entry in cache.
    Therefore, I have moved all my variables (mandatory + optional) into default values section. Now when I run query with say single company code (which is single mandatory variable), it builds cache as required. Now when i rerun query for same company code and specific material type (optional variable) (which is actually subset of first cache that we just built), it actually doesn't hit the cache, instead creates new cache entry as selection under our query name.
    Any ideas why subset of "Optional variables" are not hitting cache in my case? Any guidelines regarding how variables should be placed for cache query?
    Thanks.
    Abhijeet

    I think I found my own answer. Here are the findings:
    1. Subset of navigation will hit cache ONLY IF we are running for variables / fields that are in rows. In my case I was adding a value for variable which was in free chars and not in rows.
    2. If I have built two cache objects - say for plants 1 - 1000 and plants 1001 - 2000...and then I run for plants 500 - 1500, then it won't utilize both cache objects...Instead it will create a new one. BI is not intelligent enough to consolidate two cache objects at this moment.

  • Cache Mode Settings Transport

    Hello,
    We are planning to implement the new BLOB/Cluster Enhanced Cache Mode setting.  I plan to use the Query Mass Maintenance feature of RSRT to change the setting for all existing queries of an infoprovider.  My question is will this action alone generate a transport?  If so what objects are in the transport?  Will the transport grab all the infoprovider queries?
    Thanks,
    TMS

    Hello,
    No. A transport will not be generated, all the necessary information it is as following:
    As per note: 1026944 - New cache mode for BI 7.0 without directory.
    Go to SE16 -> run report/table RSADMIN and verify if the data is in there.
    u201CThat you can benefit from the new cache mode you have to activate it
    for all your queries. Go to RSRT -> enter query -> properties ->
    cache mode: 5 BLOB/Cluster Enhanced should be selected.
    Or via mass maintenance (transaction RSRT -> menu "Environment" -> "Mass
    Maintenance")u201D
    Regards,
    Diego Seben.

  • Cache Mode issue

    Hello,
    Can some one help me with the information also the document for the Cache modes?
    What is the difference between the cache mode 3 Persistent cache per Application server and 4. Persistent cache across each application server?
    Also i had a question : If there is a multiple Application server exists, how will the query will get cached normally with Mode 3 and 4?
    Thanks in Advance.
    Regards
    M.A

    Simple - as it says on the tin
    If you have cache per app server - then depending on the app server you have fired the query against it will either hit cache or not
    If you have multiple app servers then it's really a no brainer in this manner - go for option 4

  • Cache Mode

    i want to fill the olap cache for same web templates for reasons of performance. But if I do so, I get the following error: EXPORT_NO_SHARED_MEMORY. The export data cluster is too large for the shared
    memory.
    In Note 656060 I got this solution
    Run transaction RSRT   ->   <select your query>    ->   Properties> Change Cache Mode to either 3 or 4.
    Could you please tell which Cache Mode 3 or 4 I should choose ?
    Reagrds,
    Anita

    Hi Ryan,
    Iam trying to activate Delta Cache for some querys in RSRT.
    We have many application servers,so, as you have advised i have choosen Mode 4.
    And, ticked the check box delta cache.
    Apart from that do i need to do any other settings?
    Can you please aslo let me know what settings needs to be done for the below:
    Read Mode
    Persistence Mode
    Optimization Mode
    It'll be very helpful for me.
    Thanks,
    Nisha

  • Cache mode settings

    Hi all,
      My requirement is i have change the cache mode settings of particula query from cache mode 1( Main Memory Cache Without Swapping ) to cache mode 3 (Persistent Cache per Application Server).
      Here my question is can i transport these settings to the production system or should i do this cache mode settings in my production system itself.
    Thank you very much for your suggestions.
    Regards
    Prasad

    Hi ,
    After u save the settings in the cache mode u can very well
    transport it to the production system
    Assigning Points is the way of saying Thanks in SDN
    Regards ,
    Subash Balakrishnan

  • BW cache mode under RSRT

    Hi all,
      Which cache mode is better for good performance? I went thru help.sap.com and I got more confused.
    If possible please let me know the differences in a plain english.
    Regards,
    N.S.

    Hi N.S,
    Go over pizzamans post so that you can understand what exactly the factors to decide for cache mode and then you can decide which mode to use according to query performance.
    If you go to transaction RSRT and in there the query properties then you can select the cace modes.
    0.Cache inactive.
    1.Memory cache without swap.
    2.Memory cache with swap.
    3.Persistant cache per application server.
    4.Persistant cache across each application server.
    Generally cache mode does increase performance of queries but you should know what cache mode to apply to which queries. There is a standard rundown I am giving you I hope it will be useful in you scenario
    1. If your data changes frequently: Then use the 0 mode.
    2. If there are many users and many navigations based on that query: then u can use any mode except 0.
    3. If you have large result set in your query (E.g HR): then you can use 2,3,4 mode(I recommend4) but 0 and 1 may not be useful.
    I hope these insigts are useful.
    Regards,
    Nikhil
    Message was edited by: Nikhil

  • Caching modes and details in repository

    hi all,
    can any one please explain what is the uses of caching modes in repository ?elaborate it.
    Thanks
    Regards,
    Shya

    Hi Shya,
    First, there are two types of cache for each item descriptor:
    [1].*Item Caches*:Item caches hold the values of repository items, indexed by repository IDs. An item cache entry is invalidated when that item is updated.
    [2].*Query Caches*:Query caches hold the repository IDs of items that match given queries. When a query returns repository
    items whose item descriptor enables query caching, the result set is cached as follows:
    --The query cache stores the repository IDs.
    --The item cache stores the corresponding repository items.
    Cache Modes:For example possible values are:
    we can set <item-descriptor name="xyz" cache-mode="simple/disabled/inherit/locked/distributed/distributedJMS/distributedHybrid">....
    simple caching handles caches in each server/VM locally; no attempt is made to synchronize updates across multiple server instances.
    disabled is used when you dont want any caching on your repository and want your application to pick data everytime from your repository, like inventory to insure that inventory data is always up to date across server instances.
    inherit is used when our item-descriptor have any super item-descriptor [as per concept of item descriptor inheritance], in this case our item descriptriptor use the cache mode of super item-descriptor.
    -RMishra
    locked caching uses read and write locks to synchronize access to items stored by multiple caches, so that only one VM should update cache at a time.
    ( distributed )Distributed TCP caching uses TCP to broadcast cache invalidation events (cache invalidation event means event to update cache data) to all servers in a cluster(group of servers).
    ( distributedJMS )Distributed JMS caching uses JMS to broadcast cache invalidation events to all servers in a cluster.
    ( distributedHybrid )Distributed hybrid caching uses TCP to send cache invalidation events only to those servers that are known to cache the target items. Hense all server's cache data of item-descriptor not going to update.
    Note: Item descriptors within an inheritance tree share the same item cache. Queries that include derived item properties are never cached. Default caching mode is simple.

  • Exchange 2010 all mail clients with internal cached and internal non-cached mode users having connection status issues, login prompt -- external is fine either way

    Hello,
    I'm seeing an issue that started this past Monday with no recent change to our environment. 
    External Outlook Anywhere users and Mobile users, OWA users are unaffected.
    Internal Users are affected when using Outlook of any version, 2010 or 2013.
    -Internal Users normally log into their workstation with their ad credentials, domain joined machines. Outlook opens without credentials prompting ideally.
    1 . Using Cached Mode:
    a. Login Prompts, slowness - Since Monday, users are getting prompted to login. The prompt goes away after logging in at startup. It is also causing high CPU
    on the workstations.
    b. Free/Busy, Out of Office doesn't work. I can, however complete auto-setup for a new user, so autodiscover is not completely down for internal users.
    c. Checking Connection Status shows connecting status on highlighted entry below without ever establishing connection (just goes away).
    The outlook icon in the system tray says "Outlook is requesting data from the server":
    2. Using Non-cached mode 
    a. No Login Prompt at startup, business as usual
    b. Free/Busy, Out of Office works fine. Autodiscover is fine.
    c. Checking Connection Status shows normal except, it has "casarray URL, then status is referral" it seams to flicker this constantly then go away intermittently.
    d. Main issue in non-cached mode is, sometimes a user will log into windows, open outlook and it will not open and says "server is unavailable. Retry, work offline, or cancel" I can try re-opening, same message.
    Only after logging out of windows, logging back in, I can get back into outlook. This is not every time, or consistent with specific users, but random. 
    3. Lync Pop up  for credentials often, though entering the password.
    URLs are correct. Autodiscover, EWS, etc. 
    Already tried bypassing our loadmaster load balancer with host files on clients. same issue regardless of casarray node. 
    Not sure what is going on.
    Josh

    You have a hybrid configuration with Office 365, right?  You didn't provide this valuable piece of information.
    In Exchange Online PowerShell run this command:
    Get-OrganizationConfig | FL PublicFoldersEnabled
    If the value is "Remote" then users with Exchange Online mailboxes are looking to on-premises public folders.  Be sure that you have legacy pubic folder interoperability properly configured.
    http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Outlook 2007 cached mode not working for old exchange 2003 users

    For some reason outlook isn't receiving emails straight away when in cached mode for users which we moved (few years ago) from exchange 2003 to 2007 (we now have everyone on exchange 2010). I checked the security tab in AD and compared new and old users
    and the permissions are completely different.
    Creating a new AD account and linking the old email account to it, fixes the issue but that's not really an option for over 100 users.
    Has anyone else had this issue?

    Hello,
    What's the difference between the permissions?
    Can the users receive emails from OWA?
    In addition, please make sure your Outlook 2007 has installed the latest update. And try to use
    outlook/cleanips and check if it helps. See:
    http://support.microsoft.com/kb/968773/en-us
    Best Regards,
    Steve Fan
    TechNet Community Support

  • Outlook cached mode, shared calendars, permissions and sync errors

    We have the following environment -
    Exchange 2010 SP2, no public folder DB; Outlook 2010 sp1 cached mode.
    under very specific circumstances, but unfortunately a common circumstance, we're getting sync errors -
    15:59:56 Synchronizer Version 14.0.6126
    15:59:56 Synchronizing Mailbox 'Nigel'
    15:59:56 Synchronizing server changes in folder 'Naomi - Calendar'
    15:59:56 Downloading from server 'outlook.cri.camres.org'
    15:59:56 Error synchronizing folder
    15:59:56                                 [80070005-508-80070005-560]
    15:59:56                                 You do not have sufficient permission to perform this
    operation on this object.  See the folder contact or your system administrator.
    15:59:56                                 Microsoft Exchange Information Store
    15:59:56                                 For more information on this failure, click the URL below:
    15:59:56                                
    http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80070005-508-80070005-560
    15:59:56 Done
    This occurs if Naomi shares her Calendar with me, without granting me read "Full Details", if she changes the permissions and allows me to read Full Details, the sync error goes away.
    It's repeatable, i have tested it with a few users sharing calendars with each other, and changing permissions.
    The peculiar thing is that Naomi is in My Team, so her calendar is listed under Team Calendar,  I get no sync errors, it's only when I add Naomi's Calendar as a Shared Calendar and don't have read Full Access permission that the sync errors appear.
    User's don't necessarily want to give Full Access to their Calendars, so that's not really a viable work around for us, this smells very much like a bug with outlook, is anyone else seeing this?

    Hi
    Thanks for sharing
    Cheers
    Zi Feng
    TechNet Community Support

Maybe you are looking for