Agents fetching limited records after scheduling in OBIEE 11g.
Info: The number of rows returned when a report is run (downloaded) is different than when it is emailed to the end user via scheduling.(limited to 75 rows/records)
Description: When you run a report online, the output shows the correct number of records. However, when scheduling the Analysis Agent , the email content shows only 75 records, some expected rows are missing.
Cause: The issue is caused by the following setup:
MW_HOME/instance/Instance1/config/OracleBIPresentationServicesComponent/coreapplication_obips1/instanceconfig.xml file,
there is an entry that controls how many records could be delivered. In this case it is defaulted to 75.
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
Scenario:
Log into /analytics.
Run the report in question and observe that the number of records are greater than 75.
Now, schedule the report using the Analysis Agent.
The emailed report will have only 75 rows or records.
Please note that the fix has to be done through the BI Enterprise Manager not by modifying the instanceconfig.xml.
The instanceconfig.xml should look like below tag before modifying through EM.
<Views>
<Pivot>
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
<DefaultRowsDisplayedInDownload>25000</DefaultRowsDisplayedInDownload>
<DisableAutoPreview>false</DisableAutoPreview>
<MaxCells>1000000</MaxCells>
</Pivot>
<Table>
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
<DefaultRowsDisplayedInDownload>25000</DefaultRowsDisplayedInDownload>
<MaxCells>1000000</MaxCells>
</Table>
</Views>
The Solution:
To increase this value, please follow these steps:
1. Log in to Fusion Middleware Enterprise Manager.
2. Navigate to Coreapplication => Capacity Management => Performance tab.
3. Look for this setting.
[Maximum Number of Rows Per Page to Include].
4. Change this value to 25000 and ensure to click the "APPLY" button.
5. Followed by clicking "Activate Changes" , restart the BI Server (all of the coreapplication components).
Info: The number of rows returned when a report is run (downloaded) is different than when it is emailed to the end user via scheduling.(limited to 75 rows/records)
Description: When you run a report online, the output shows the correct number of records. However, when scheduling the Analysis Agent , the email content shows only 75 records, some expected rows are missing.
Cause: The issue is caused by the following setup:
MW_HOME/instance/Instance1/config/OracleBIPresentationServicesComponent/coreapplication_obips1/instanceconfig.xml file,
there is an entry that controls how many records could be delivered. In this case it is defaulted to 75.
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
Scenario:
Log into /analytics.
Run the report in question and observe that the number of records are greater than 75.
Now, schedule the report using the Analysis Agent.
The emailed report will have only 75 rows or records.
Please note that the fix has to be done through the BI Enterprise Manager not by modifying the instanceconfig.xml.
The instanceconfig.xml should look like below tag before modifying through EM.
<Views>
<Pivot>
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
<DefaultRowsDisplayedInDownload>25000</DefaultRowsDisplayedInDownload>
<DisableAutoPreview>false</DisableAutoPreview>
<MaxCells>1000000</MaxCells>
</Pivot>
<Table>
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
<DefaultRowsDisplayedInDownload>25000</DefaultRowsDisplayedInDownload>
<MaxCells>1000000</MaxCells>
</Table>
</Views>
The Solution:
To increase this value, please follow these steps:
1. Log in to Fusion Middleware Enterprise Manager.
2. Navigate to Coreapplication => Capacity Management => Performance tab.
3. Look for this setting.
[Maximum Number of Rows Per Page to Include].
4. Change this value to 25000 and ensure to click the "APPLY" button.
5. Followed by clicking "Activate Changes" , restart the BI Server (all of the coreapplication components).
No comments:
Post a Comment