Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

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

Exceeded configured maximum number of allowed input records. Error Codes: EKMT3FK5

Received Response
66
Views
6
Comments
Gabriele Boccassini
Gabriele Boccassini Rank 1 - Community Starter
edited November 8 in Oracle Analytics Cloud and Server

Hi all,

I'm getting below error while running OAC reports with a pivot table.

Exceeded configured maximum number of allowed input records. Error Codes: EKMT3FK5

The compute size configured is 6 OCPUs.

Is it possible that the problem is related to this limit reported in the documentation?

image.png

In this case, why does the problem not arise if I use a normal table instead of the pivot table? What does this limit indicate?

Alternatively, is it possible that the problem is related to a limit on the maximum number of cells that can be displayed in a pivot table (although I didn't find this limit in the documentation)?

Thanks

Tagged:

Answers

  • GayathriAnand-Oracle
    GayathriAnand-Oracle Mod

    The documented limits for number of rows based on OCPUs are based on 40 column limit in the workbook/report. So if you have more than 40 columns, you could be exceeding the limit even thought the row count is within documented limit. This information is going to be documented in the product documentation shortly.

    Thanks

    Gayathri

  • Gabriele Boccassini
    Gabriele Boccassini Rank 1 - Community Starter

    Thanks for your reply Gayathri.

    This is not the case, I have less than 40 columns in the pivot table.

    I don't understand what the documentation means by "the maximum number of summarized rows returned from the data source that are displayed". It is not the maximum number of rows that can be displayed in analysis, because if I use a normal table instead of a pivot table it's ok. So, what does it mean?

    I noticed that if I try to execute the query generated by OAC directly on DB, it returns more than 500.000 rows but in the pivot table visualization obviously they become much less (shifting some informations from row to column). So, in any case fewer than 500.000 rows would be displayed.

    Thanks

  • Federico Venturin
    Federico Venturin Rank 7 - Analytics Coach

    Hi @Gabriele Boccassini ,

    There appears to be a limit on the maximum number of cells (number of rows * number of columns) that a pivot table can have in OAC. This limit is not documented, users/administrators can't update it, and only Oracle knows if the value is going to change according to the number of OCPUs. If you want to continue using a pivot table, the only solution is to reduce the number of cells.

    "the maximum number of summarized rows returned from the data source that are displayed" refers to the number of logical rows returned by a request (the tool retrieves X physical rows from the data sources, then applies aggregations/filters/transformations as required and specified in the data model to get Y logical rows).

  • Gabriele Boccassini
    Gabriele Boccassini Rank 1 - Community Starter

    Hi Federico, thanks for your reply.

    Let's give an example: I execute the query generated by OAC on DB and it returns 380.000 rows. These records are displayed in a pivot table and become 12000 rows (shifting some informations from row to column). In this case "the number of summarized rows returned from the data source that are displayed" is 12000?

    Thanks

  • Federico Venturin
    Federico Venturin Rank 7 - Analytics Coach

    @Gabriele Boccassini

    No. It refers to the number of rows in the result set (logical rows), which is always in plain tabular format.

    The pivot is created AFTER the result set has been generated and returned to your web browser.

    In your case, the number of logical rows is probably the same as your physical rows (380000). To be sure about it, I recommend to enable and have a look at Usage Tracking data, or analyze query session logs.

  • Christian Berg -Oracle
    Christian Berg -Oracle Mod
    edited November 11

    @Gabriele Boccassini Late to the party, but: There's much more to what's happening than just number of rows. Federico hinted at cells, but there's more than that involved.

    If you look at the official OBI documentation which still explained things in detail, you can see all the settings which play in to that:

    https://docs.oracle.com/middleware/12211/biee/BIESG/GUID-E158301D-67F3-495D-BEB7-B81FFDBA725A.htm

    Since the documentation no longer explains which of these parameters is set to what value for OAC, let alone what the parameters for DV are compared to Answers, I'd suggest opening a Service Request (high priority, don't go with a random level 3) and demand a clear explanation for your use case. You have to provide exact numbers and information from your side and demand and equally clear answer.

    Alternatively @Bret Grinslade - Oracle Analytics-Oracle may feel generous and share the detail settings here :)

    Edit: corrected the doc link