Oracle Transactional Business Intelligence

Home› Oracle Analytics› Oracle Analytics Forums› More Solutions› Oracle Transactional Business Intelligence

Categories

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

Any way to bypass the row Limitation

Received Response
471
Views
11
Comments
Robin Friedberg O'Connor
Robin Friedberg O'Connor Rank 3 - Community Apprentice
in Oracle Transactional Business Intelligence

Summary

Bypass Row Limitation

Content

Is there anyway to bypass the row limitation?  There are times I need to be able to analyze more than 25,000 rows of data.  This is causing a lot of work to divide reports up to be able to get to all of the information needed. 

Tagged:
«1

Answers

  • rajArun
    rajArun Rank 5 - Community Champion

    Hi,

    Are you using a OTBI report? We had to create a BI report to by pass the issue.

    ~Arun

  • Chris Dabel
    Chris Dabel Rank 2 - Community Beginner

    Hi,

    The row limitation cannot be changed. Do you have to analyze all the rows? Or can you get them via another method, then view them in Excel?

    Could you please explain what you mean by "analyze more than 25,000 rows of data"? What kind of analysis do you need to do? The answer will help us be able to advise on alternate ways of getting this information. For example, we have the the Oracle BI Cloud Connector, which may help you meet your business requirement. Here is the BI Cloud Connector overview page.

    Also, as Arun says, you may try using BI Publisher, if you can, to generate the report you need.
     

    Thank you,
    Chris Dabel
    Oracle Fusion Support

  • Neil Peacock
    Neil Peacock Rank 2 - Community Beginner

    Hi Robin,

    If you export the report as a Data - CSV file, you will have a higher limit of rows. I believe this is 65,000. However this method can lose some formatting and will be exported in the order you have the data in the criteria tab, rather than in the results tab. So you might have to make your criteria match your results order and import into excel from text to continue to use any vlookups to older documents.

    This method will allow you to analsyse up to 65,000 rows on your preexisting report.

    Neil

     

     

  • Robin Friedberg O'Connor
    Robin Friedberg O'Connor Rank 3 - Community Apprentice

    Thanks, I appreciate the tip and I will give this a try.  I have been avoiding using BI Publisher for this since it is a report that one of our end users runs--BI Publisher is too difficult for this user to manage.  They want to extract all absences between a given time period and their business unit is large. 

  • Chris Dabel
    Chris Dabel Rank 2 - Community Beginner

    Great point, Neil! Thank you for these tips!

    -Chris

  • Robin Friedberg O'Connor
    Robin Friedberg O'Connor Rank 3 - Community Apprentice

    Neil--Exporting as CSV worked!  Thank you so much for the tip.  This saved me a lot of time!

  • Neil Peacock
    Neil Peacock Rank 2 - Community Beginner

    Your welcome, glad I could help. We had this issue in another Oracle system when exporting and thankfully it holds true here too.

  • rajArun
    rajArun Rank 5 - Community Champion

    Hi Neil,

    Thanks for the tip. I believe in newer versions of Excel (2013, 2016 etc), we can view more than 65000 records.

    Thanks,

    Arun

  • Neil Peacock
    Neil Peacock Rank 2 - Community Beginner

    Hi Arun,

    The limitation is not with Excel itself, it is with the export from Oracle being configured to have a maximum row count. These could be changed in the config, however I have been advised on an SR that this is very rare due to the fact that it will get overwritten with patches/updates etc

    Thanks

    Neil

  • rajArun
    rajArun Rank 5 - Community Champion

    Thanks Neil. That's an interesting point.

    The excel Template for BI reports has a similar limitation. 

    Regards,

    Arun