2 Replies Latest reply on Mar 26, 2018 7:09 AM by Sagar Tippe

    Report Taking long time to run

    2693347

      Hi All,

       

      Can anyone explain me about tag below in details.When i can add this in instance config file.

       

      <Cube>
      <CubeMaxRecords>100000000</CubeMaxRecords>
      <CubeMaxPopulatedCells>100000000</CubeMaxPopulatedCells>
      </Cube>

       

      I have one issue like in my report only 344 records which is running fine when i ran that in database(executing OBIEE Query), but same thing when i ran through analytics its keep on running and not giving any result, Every time i am cancelling  it after 10 mins.

       

      Can anyone tell me what is the issue here and is the above tag help me to solve that issue?

       

      Thanks

        • 1. Re: Report Taking long time to run
          Gianni Ceresa
          • CubeMaxRecords — Specifies the maximum number of records that are returned by an analysis for the view to process. This roughly governs the maximum number of cells that can be populated in a view; unpopulated cells in a sparse view do not count. The default is 40000.
          • CubeMaxPopulatedCells — Specifies the maximum number of cells in a view that can be populated with data from the Oracle BI Server. The default is 120000.

          From the doc, always a good place where to look for answers

           

          Setting them to 100'000'000 sounds like you want to do data pump via OBIEE: wrong tool for the wrong need.

          As you can see How to Ask Questions in Developer Community Spaces there are multiple information you can provide when asking a question to get some answers, otherwise it's just random guesses.

          • 2. Re: Report Taking long time to run
            Sagar Tippe

            First: Why the numbers configured are in thousands billions? Use SQLLDR for data pumping, you will surely get a better performance than OBIEE.

             

            Second: Definitely issue is not at DB end. Try creating a complete new analysis by pulling one column at a time, you can check where the problem lies in.

             

            Third: Try taking physical SQL from BI diagnostics, and run the same in SQL developer.

             

            Hope this helps.

            Sagar