While Rollup is goingon Can we execute the query

Hello All
We have a cube and aggregates built on this cube and daily in my Process chain we have step Rollup.
Now while Rollup is goingon Can we execute the query which is builut on the same cube? Will the cube will be locked?
Can we excute query while load is goingon to this cube?
Regards
Balji

Hi Balaji,
You can execute a query when the roll up is going on. The new data is available to the report only when the rollup is complete, but this will not create locks.
Hope this helps...

Similar Messages

  • Can we execute the Reporting while the data is loading into that ODS/Cube.

    Hi Friends,
          Can we execute the reports on particular ODS/InfoCube in the following cases
    1) When the data is loading into that ODS/Infocube.
    2) When we are Archiving the data from that ODS/Infocube
    Thanks & Regards,
    Shaliny. M

    Hi Shaliny,
    First of all you are in the wrong forum, in Business Intelligence Old Forum (Read Only Archive) you will find better support.
    In case you are loading data in an infocube you will be able to have report only until the request that has the icon ready for reporting filled. In case of an ODS object i don't think you will be able to have valid reporting since the ODS data firstly needs to be activated.
    Nevertheless please post your question in the above link.
    Kostas

  • While executing the query in the web template I am  facing below issue

    Hello SAP geniuses,
    Please help me on my issue  ,
    while executing the query in the web template i am  facing below issue.
    The variable for characteristic (region) is appearing but this characteristic (region) is not appearing in the free characteristic zone  but when we are executing the query with out webtemplate it is showing both variable and free characteristic
    can anybody help us to identify what is the issue with the web template.
    Thanks
    Alok

    Hi,
    Plz check ur report and execute at the designer and take its technical name and go to RSRT. log out and log in and try..
    if not check ur authorisation.
    Regards....KP

  • Serious system error while executing the query: java.lang.OutOfMemoryError

    From ALSB, we are trying to insert records in a table, by calling the ALDSP webservice. It is working fine when the xml (ie., given as input to the ALDSP webservice) is small. But facing the following error when the input xml size is large.
    <ALDSP> <BEA-000000> <Product> <Serious system error while executing the query:
    {ld:ABC/Test}createTest:1
    java.lang.OutOfMemoryError: Java heap space
    We do not want to increase the heap size. Is there any other way we can solve this problem?

    In logical dataservice of ALDSP we have created a procedure called createTest, which is used to insert mulitple rows in the table. We have created a webservice for that logical DataService.
    Using the ALSB, we are calling the webservice -> createTest Operation and we are passing xml as input to that createTest function.
    Input xml:
    <ns1:createTest>
    <ns1:createTemps>
    <ns0:createTemp>
         <ns0:field1>1</ns0:field1>
              <ns0:field10>test1</ns0:field10>
    </ns0:createTemp>                
    <ns0:createTemp>
         <ns0:field1>2</ns0:field1>
              <ns0:field10>test2</ns0:field10>
    </ns0:createTemp>
         </ns1:createTemps>     
    </ns1:createTest>
    each ns0:createTemp represent a row that need to be inserted in the table.
    When the number of ns0:createTemp is less ( when the number of rows that need to be inserted is less) then no problem occurs, it is getting inserted properly. But when there are more number of ns0:createTemp then we are getting the following error
    <ALDSP> <BEA-000000> <Product> <Serious system error while executing the query:
    {ld:ABC/Test}createTest:1
    java.lang.OutOfMemoryError: Java heap space

  • Issue While executing the Query for Pagination using ROWNUM with like

    Issue While executing the Query for Pagination using ROWNUM with like.
    Database is Oracle11G.
    Oracle Database Table contains 8-9 lakh records
    1) SQL equal (=)
    SELECT /*+ FIRST_ROWS(n) */ ROWNUM RNUM, A.* FROM LINE A
    WHERE A.REFERENCE = 'KMF22600920'
    Execution Time:- 0.00869245 seconds
    Returns 2 resultsets
    2) SQL like (one %)
    SELECT /*+ FIRST_ROWS(n) */ ROWNUM RNUM, A.* FROM LINE A
    WHERE A.REFERENCE = 'KMF22600920%'
    Execution Time:- 0.01094301 seconds
    Returns 2 resultsets
    3) SQL like (two%)
    SELECT /*+ FIRST_ROWS(n) */ ROWNUM RNUM, A.* FROM LINE A
    WHERE A.REFERENCE like '%KMF22600920%'
    Execution Time:- 6.43989658 seconds
    Returns 2 resultsets
    In Pagination, we are using Modified version of SQL Query 3) with ROWNUM as mentioned below :-
    4) SELECT * FROM (
    SELECT /*+ FIRST_ROWS(n) */ ROWNUM RNUM, A.* FROM LINE A
    WHERE REFERENCE like '%KMF22600920%' AND ROWNUM <= 20 ) WHERE RNUM > 0
    Execution Time:- Infinite
    ResultSets:- No as execution time is infinite
    a) Instead of like if we use = in the above query it is returning the 2 resultsets (execution time 0.02699282 seconds)
    b) Instead of two % in the above query, if use one example REFERENCE like 'KMF22600920%' it is returning the 2 resultsets (execution time 0.03313019 seconds)
    Issue:- When using two % in like in the above query i.e. REFERENCE like '%KMF22600920%' AND ROWNUM <= 20 ) , it is going to infinite.
    Could you please let us know what is the issue with two % used in like and rownum
    5) Modified version of Option1 query (move out the RNUM condition AND RNUM <= 20)
    SELECT * FROM (
    SELECT /*+ FIRST_ROWS(n) */ ROWNUM RNUM, A.* FROM LINE A
    WHERE REFERENCE like '%KMF22600920%' ) WHERE RNUM > 0 AND RNUM <= 20
    Execution Time:- 7.41368914 seconds
    Returns 2 resultsets
    Is the above query is best optimized query which should be used for the Pagination or still can improve on this ?

    This would be easier to diagnose if there was an explain plan posted for the 'good' and 'bad' queries. Generally speaking using '%' on both sides precludes the use of any indexes.

  • Can we execute a query in resultset while loop

    can we execute a query in resultset while loop
    for ex:
    rs=st.executeQuery("SQL");
    while(rs.next())
    rs1=st.executequery("SQL1");
    while(rs1.next())
    }

    If you do this, you lose "rs". Create a second
    Statement object for the other query.This is right. We have done it many times, It is not the issue as long as you use different statement with in the body of the loop

  • Can we execute a query in resultset of while loop

    can we execute a query in resultset while loop
    for ex:
    rs=st.executeQuery("SQL");
    while(rs.next())
    rs1=st.executequery("SQL1");
    while(rs1.next())
    }

    yup no problem..if it doesn work declare the second one as st1

  • JDBC- can u execute a query while processing results

    can you execute a query in the while loop of a different resultSet?
    e.g.,...
    line2= ("Select teamName, played, won, lost, draw, forfor, against, points from leaguetable where tourId = " + tourId);
    query4 = stmt.executeQuery(line2);
    while (query4.next())
    teamName = query4.getString(1);
    playedTemp = query4.getString(2);
    played = Integer.parseInt(playedTemp);
    wonTemp = query4.getString(3);
    won = Integer.parseInt(wonTemp);
    lostTemp = query4.getString(4);
    lost = Integer.parseInt(lostTemp);
    drawTemp = query4.getString(5);
    draw = Integer.parseInt(drawTemp);
    forforTemp = query4.getString(6);
    forfor = Integer.parseInt(forforTemp);
    againstTemp = query4.getString(7);
    against = Integer.parseInt(againstTemp);
    pointsTemp = query4.getString(8);
    points = Integer.parseInt(pointsTemp);
    for (int i=0; i<homeTeams.length; i++){
    if(teamName.equals(homeTeams)){
    homeTeamScoreInt = Integer.parseInt(homeTeamScore[i]);
    awayTeamScoreInt = Integer.parseInt(awayTeamScore[i]);
    if(homeTeamScoreInt > awayTeamScoreInt){
    played = played + 1;
    won = won + 1;
    forfor = forfor + homeTeamScoreInt;
    against = against + awayTeamScoreInt;
    points = points + 3;
    line3 = ("Update LEAGUETABLE set played = " + played + ", won = " + won + ", forfor = " + forfor + ", against = " + against +
    ", points = " + points + " where tourid = " + tourId + " AND teamName = '" + teamName+ "'");
    stmt.executeUpdate(line3);
    it only works once, it stops at the end of the while loop, i.e., it doesnt loop around the resultSet like it should.

    do you mean for this part...
    query4 = stmt.executeQuery(line2);
    while (query4.next())
    surely the data is stored in the resultSet ??
    or do you mean this part...
    stmt.executeUpdate(line3);

  • Can I stop a report from Re-executing the query when I go back to that page

    I have a report that has a complicated query and looks at a lot of information to display the results. This query then links of to show details of individual items that were displayed in the result. But when I hit the back button on the browser, it executes the query again and it takes a while for the page to load.
    Is there any way to stop this and only execute the query when the User pushes a Button on the page else display the previous results.
    Thanks
    Sriram

    Another alternative is to make that detail link open in a popup window using
    javascript:popupURL(...);This way, the complicated report page is always visible.

  • In ST03 , how can i see the Query name, user id,how many times executed the

    HI Experts,
    In ST03 , how can i see the Query name, user id,how many times executed the query.
    these details how do i get from the above transaction.
    EX:-if there is one report name X,I want to know how many users had executed X report today,weekly,monthly.
    ex:-query userid total number of execution
    sales order 0000555 5 times
    custmer 05855 2 times
    fast reply will be appreciated,

    Hi,
    Look here:
    http://help.sap.com/saphelp_nw04/helpdata/en/3b/54df4204892a78e10000000a155106/frameset.htm
    Also check these:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/2d/b8be3befaefc75e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/25/ece73a39e74d27e10000000a114084/frameset.htm
    Hope this helps..
    Bye
    Dinesh

  • Dump while executing the Query

    Hi,
    when I try to execute the query I get the following dump.
    ASSIGN_TYPE_CONFLICT
    Error analysis
    You attempted to assign a field to a typed field symbol,
    but the field does not have the required type.
    Pleaes assist , its urgent
    Regards,
    ANita

    Hi,
    The problem is Solved.
    If the problem is occuring while running the query,  regenerate the query through transaction RSRT.
    Regards,
    ANita

  • ORA-01722  Invalid Number while executing the Query

    Hi Friends,  need your valuable suggestions.
    We have a DSO with a   characteristic info object  ZDAT (DATA TYPE DATS)  with a reference from 0DATE.
    I am able to see the data of the info object ZDAT using LIST CUBE on the DSO.
    While using this info object ZDAT in the query moniter or bex analyzer it shows the  following errors.
    EORA-01722: invalid number .
    EError reading the data of InfoProvider.
    EError while reading data; navigation is possible   
    I>> Row: 71 Inc: NEXT_PACKAGE Prog: CL_SQL_RESULT_SET.
    Kindly please help me on this issue.

    Hello soumya
    Can you check if you have any NULL values in ZDAT in from LISTCUBE?
    If yes, check the note below
    https://service.sap.com/sap/support/notes/1327167.
    If null value is your problem, you can change the query setting for not to show the null values. Just add a filter in ZDAT to exclude "NULL"
    Regards
    Anindya

  • How can i know which index will be used when executing the query ?

    1 ) I have query in which i have 3-4 tables but there multiple index on one column .
    so how can i know which index will be used when executing the query ?
    2) I have a query which ia taking too much time . how can i know which table is taking too much time ?
    3) Please Provide me some document of EXplain plan ?

    Hi Jimmy,
    Consider the below example
    /* Formatted on 2011/02/04 21:59 (Formatter Plus v4.8.8) */
    CREATE TABLE FIRST AS
    SELECT * FROM all_objects;
    UPDATE FIRST
    SET object_name = 'TEST'
    WHERE owner != 'SCOTT';
    CREATE INDEX idx_first ON FIRST(object_name);
    SELECT *
    FROM FIRST
    WHERE object_name = 'TEST';
    It has not used index
    Execution Plan
    Plan hash value: 2265626682
    | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
    | 0 | SELECT STATEMENT | | 58678 | 7334K| 163 (4)| 00:00:02 |
    |* 1 | TABLE ACCESS FULL| FIRST | 58678 | 7334K| 163 (4)| 00:00:02 |
    /* Formatted on 2011/02/04 21:59 (Formatter Plus v4.8.8) */
    SELECT *
    FROM FIRST
    WHERE object_name = 'emp';
    This has used the index
    Execution Plan
    Plan hash value: 1184810458
    | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
    | 0 | SELECT STATEMENT | | 1 | 128 | 1 (0)| 00:00:01 |
    | 1 | TABLE ACCESS BY INDEX ROWID| FIRST | 1 | 128 | 1 (0)| 00:00:01 |
    |* 2 | INDEX RANGE SCAN | IDX_FIRST | 1 | | 1 (0)| 00:00:01 |
    From this we can come to the conclusion that, whether to use one index or not by oracle
    would also depend on the data which is present in the table. This has to be this way as
    we see in the bind peeking, if oracle sticks to only one plan, say only use the full table
    scan, it would be a performance hit when it searches for the second query ie where object_name
    ='emp';
    2.
    If we have a query like below.
    select * from emp
    where upper(ename) = upper(:p_ename);
    Evenif we have the index on ename column, oracle wouldn't be able to use the index, as there is a function in the predicate column. If you need oracle to use the index, we need to create a function based index as below.
    Create index idx_ename on emp(upper(ename));
    Regards,
    Cool

  • Can we execute the BAPI in SE37?.

    Can we execute the BAPI in SE37?.

    Yes Satish. We can execute BAPI's via transaction SE37.
    But for explicit commit we have to execute BAPI_TRANSACTION_COMMIT
    To do so:
    1. SE37.
    2. Menupath: Function Module -> Test -> Test Sequences
    3. In the popup screen, give the BAPI Name and then BAPI_TRANSACTION_COMMIT.
    These FM's will be executed in sequence.
    Hope this helps.
    Kind Regards
    Eswar

  • 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.

Maybe you are looking for