Max number of section exceeded in obiee 11g — Oracle Analytics

Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Max number of section exceeded in obiee 11g

Received Response
71
Views
8
Comments
3167974
3167974 Rank 4 - Community Specialist

hi,

we have a  requirement to show the columns in section in table view .but as column has huge no of records its throwing me below error :-

Exceeded configured maximum number of allowed input records

and  we dont want to increase the size of max visible section in instance config.xml file as it would impact the performance of obiee. so we just want to show only say for ex 200 section in report level and after exporting into different format they should be able to see all the records.

Answers

  • Gbenga Ajakaye
    Gbenga Ajakaye Rank 5 - Community Champion

    See this thread. It might provide you with some insight.

    OBIEE 11g: Exceeded configured maximum number of allowed input records

  • 3167974
    3167974 Rank 4 - Community Specialist

    hi,

    we dont want to increase the section size in the instanceconfig.xml file as its impacting the performance of obiee . so what we have new req is

    just show 200 section in report level and if suppose we have more than 200 section records then while exporing it should show all the records in the export. please let me know whether its possible.

  • EmmanuelMash
    EmmanuelMash Rank 4 - Community Specialist

    Hi

    You mention when you increase these values you have performance issues, that is something you have to tune and narrow down what exactly is causing the issue and I don't think its the instanceconfig.xml changes.

    From your response above I think what you are trying to do is set table properties for rows per page setting. The other thing to consider is to have a look at the actual tag in the instanceconfig that is causing the exceeded max number allowed error e.g is it the <CubeMaxRecord> which specifies the number of records returned for a view or  <MaxVisibleSections> default is 25 sections etc

    Regards

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    You cant kill both wishes with one analysis. Either it's rendered or not.

  • 3167974
    3167974 Rank 4 - Community Specialist

    to remove this error as  Exceeded configured maximum number of allowed input records  we just one to show 200 records so as while exporting we can see more records in different format .

  • 3167974
    3167974 Rank 4 - Community Specialist

    hi,

    i have one question if we increase no of max visible section from 500 to say 5000 and cube max records to 1000000 then  whether obiee will put load on server /impact the performance

  • EmmanuelMash
    EmmanuelMash Rank 4 - Community Specialist

    This is different from a variable declaration where you will be reserving a space in memory. You only make use of the max records when you get to that value. In your case you have defaults that is why you are having problems. I am sure you have a dev server, play with the different metrics that way you will know the impact of making such changes.

  • 3167974
    3167974 Rank 4 - Community Specialist

    yes we are on dev