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

Export Issue for OBIEE reports where rows is more than 65000

Received Response
21
Views
3
Comments
User_5YLTI
User_5YLTI Rank 4 - Community Specialist
edited Aug 13, 2024 5:27PM in Oracle Analytics Cloud and Server

We have an OBIEE version of 12.2.1.4 in linux server where most of the reports fetch data more than 65000. We have raised an Oracle SR where they have proposed the following solution :

  <XMLP>

  <InputStreamLimitInKB>0</InputStreamLimitInKB>

  <ReadRequestBeforeProcessing>false</ReadRequestBeforeProcessing>

  </XMLP>

  also in config.xml I did the following change:

  <MessageProcessor>

  <SocketTimeout>5000</SocketTimeout>

  </MessageProcessor>

In  Instanceconfig.xml :

  <ODBC>

  <ResultRowLimit>65000</ResultRowLimit>

  </ODBC>

Again in Oracle Doc the following solution is suggested :


<XMLP>
<InputStreamLimitInKB>0</InputStreamLimitInKB>
<ReadRequestBeforeProcessing>true</ReadRequestBeforeProcessing>
</XMLP>

To:
<XMLP>
<InputStreamLimitInKB>2048</InputStreamLimitInKB>
<ReadRequestBeforeProcessing>false</ReadRequestBeforeProcessing>
</XMLP>

Save and exit the file.

Start the OBIEE, and test the same report once more.
One should be able to export more than 65000 rows.

None of the solutions has worked for me. Please suggest what can be done if data count is more than 65000

Answers

  • Gianni Ceresa
    Gianni Ceresa Mod

    Please remove copy/paste content from MOS documents. You can't post it in a public forum, if you want to post that content you would need to move your thread to

  • User_5YLTI
    User_5YLTI Rank 4 - Community Specialist

    I hope I have removed the line properly. Now I have only mentioned what I have done and what's suggested

  • Gianni Ceresa
    Gianni Ceresa Mod

    The "suggested solution" given by Doc ID 2161550.1 is the issue ...

    That piece of information is accessible only to people having a valid support contract.

    So simply says you applied the solution of that Doc ID and still it isn't working.