OBIEE 12c: Exceeded configured maximum number of allowed input records

How to Fix Error Exceeded Co Maximum number of allowed I Records


Error:-

Solution :-


1) Go to the Instance Config file and take a backup copy of it .
2) Locate the cube section in the file, if it doesn't exist you might need to add.
3) Include the following set of code between the server instance tag.

Take a backup and modify [Domain-Home]/config/fmwconfig/biconfig/OBIPS/instanceconfig.xml

<Table>
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
<DefaultRowsDisplayedInDownload>1000000</DefaultRowsDisplayedInDownload>
<DefaultRowsDisplayedInDownloadCSV>1000000</DefaultRowsDisplayedInDownloadCSV>
<MaxCells>20000000</MaxCells>
<MaxVisiblePages>10000</MaxVisiblePages>
<MaxVisibleRows>200000</MaxVisibleRows>
<MaxVisibleSections>200000</MaxVisibleSections>
<DefaultRowsDisplayed>30</DefaultRowsDisplayed>
</Table>

<Pivot>
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
<DefaultRowsDisplayedInDownload>1000000</DefaultRowsDisplayedInDownload>
<DisableAutoPreview>false</DisableAutoPreview>
<MaxCells>20000000</MaxCells>
<MaxVisibleColumns>20000</MaxVisibleColumns>
<MaxVisiblePages>10000</MaxVisiblePages>
<MaxVisibleRows>200000</MaxVisibleRows>
<MaxVisibleSections>200000</MaxVisibleSections>
</Pivot>

To export large quantities of rows to MS Excel, increase the InputStreamLimitInKB parameter and changed the ReadRequestBeforeProcessing value to false in $DOMAIN_HOME/config/fmwconfig/biconfig/OBIJH/config.xml file, as recommended by Oracle in Doc ID 1595671.1 

<XMLP> 

<InputStreamLimitInKB>0</InputStreamLimitInKB> 

<ReadRequestBeforeProcessing>false</ReadRequestBeforeProcessing> 

</XMLP

<MessageProcessor> 

<!-- How much time worker thread should wait for a message before returning socket to the "idle" pool. Initial messages in the idle pool are handled using Java NIO Channels. --> 

<SocketTimeout>1200000</SocketTimeout> 

</MessageProcessor> 

In the obijh.properties file located in $ORACLE_HOME/bi/modules/oracle.bi.cam.obijh/env/ increase the memory reserved for JavaHost requests to 16GB 

MEM_ARGS=-Xmx16384M 

Edit the bridgeconfig.properties file, which is the configuration file for the Presentation Services Plug-In located in $DOMAIN_HOME/config/fmwconfig/biconfig/, adding the following parameters to increase the socket timeout and connection pool maximum connections 

# Number of seconds to wait for a response from sawserver 

# Default value is 360 seconds 

oracle.bi.presentation.sawconnect.ConnectionPool.SocketReadTimeoutSec = 3600 

# Maximum number of connections in pool. Default is a function of number of processors. 

# Default value is 128 

oracle.bi.presentation.sawconnect.ConnectionPool.MaxConnections = 512 

Restart OBIEE and validate the issue. 

4) If your using load balancer then perform below action plan

Take a backup of the existing configuration files mod_wl_ohs.conf. 

Increase the below parameter of <Location /analytics> and <Location /analytics-ws> to 

WLSocketTimeoutSecs 3600 

Restart OHS server and validate the issue. 

If still having the issue, increase the timeout from Oracle Load balancer "hostname". 

Contact your network team and troubleshoot network trace while running the report. This could help to understand the network breaking. 

Timeout parameter value of listener for obiee load balancer to 1800 seconds.