Oracle Communities

Oracle Analytics and AI

Child Item

OTBI Analysis fetches starting 75001 rows only -- how to increase the limit

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

Description (Required):

For one of our customer OTBI analysis is fetching only 75001 rows but for other customer it is fetching 250000 rows by default.

Please let me know how to change/control this setting

Use Case and Business Need (Required):

Customer want to fetch more rows in OTBI analysis

Enhancement Request / Service Request:

Find more posts tagged with

Needs Votes

Status: Needs Votes

Comments

DM-WSFS

Please do, this is very frustrating to have this limitation, 75k rows is not enough. 250k won't be enough at some point too.

Alyse Grant

It would be VERY helpful to be able to increase the number of lines.

User_00FBO

Hi,

This is and awful limitation in every GL audit for us where we are having +200k rows that we need to extract and send to the auditor.

Please increase and make this possible,

Farooq H Syed

Increasing the limit is very much required as by growing the data customers required more data and this has to be enhanced.

Ahmed M Ali

Running one of the detailed OTBI Reports after only one quarter Requires us to run it in 3 or may be 4 times with different parameters to split the data to be able to get the Quarter data It's a time consuming job

It's indeed a very Required Feature we hope it can be done through a profile option or Something can be increased by SR. But to limit it to 75000 Records only will keep some customers Out of using it at all

User_8RKYT

The OTBI report needs to be run multiple times per month close per day, it is extremely inefficient to only fetch 250K rows.

James Coles

Our client also requires this. 75k lines is a small amount of data

Amit Sutar

We should have option to setup the limit of records instead of defaulting the row count.

KDR

Please increase this limit to at least 250k rows. This limitation has forced us to re-write several OTBI analyses into BIP Data Models/Reports and required a lot of development time migrating the Logical SQL into Physical SQL, in order to avoid this hard limit.

Tom Strudley

Have seen this come up a number of times