Exceeded configured maximum number of allowed input records.

Issue: While trying to open a report from Analytics, you may get an error stating"

Exceeded configured maximum number of allowed input records". Description:  This error occurs when the BI server tries to fetch up more records than the limit specified in instanceconfig.xml file. Solution: We need to change the row limit in instanceconfig.xml file which is in the location MW_HOME/instance/Instance1/config/OracleBIPresentationServicesComponent/ coreapplication_obips1/instanceconfig.xml file.(The same can be increased using console itself.)

• Note: Below mentioned tags has to be included in between <security> and </security> inorder to increase the maximum display limit in reports. 

<Cube>
<CubeMaxRecords>999999</CubeMaxRecords>
<CubeMaxPopulatedCells>180000</CubeMaxPopulatedCells>
</Cube>

<Charts>
        <MaxVisibleColumns>999999</MaxVisibleColumns>
        <MaxVisiblePages>999999</MaxVisiblePages>
        <MaxVisibleRows>999999</MaxVisibleRows>
        <MaxVisibleSections>999999</MaxVisibleSections>
        <JavaHostReadLimitInKB>999999</JavaHostReadLimitInKB>
 </Charts>

<Pivot>
<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->
<DefaultRowsDisplayedInDownload>999999</DefaultRowsDisplayedInDownload>
<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->
        <MaxVisibleColumns>999999</MaxVisibleColumns>
        <MaxVisiblePages>999999</MaxVisiblePages>
        <MaxVisibleRows>999999</MaxVisibleRows>
        <MaxVisibleSections>999999</MaxVisibleSections>
<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><DisableAutoPreview>false</DisableAutoPreview>
</Pivot>

•  Restart the BI Server after making the required changes. It is better if you could restart all of the coreappliaction components.

OBIEE 11g : weblogic.management.managementexception : "unable to obtain lock server may already be running".


This error occurs in two scenarios:

1. If the server is already running.
2. If the server is not properly killed and at times it does retain some references to the .lok file under the tmp directory of the DOMAIN/server folder and the lok file is not relinquished totally.

When the server starts it checks if any .lok file in present in the tmp file.
If yes, it would try to acquire a lock on that one.

If the lock is already held by some other process, then it would throw this error.

Solution: 

1. Check the running processes which can acquire lock on the .lok files and kill them.
2. Restart the server. 

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).

BEA-141281 unable to get file lock, will retry. . 


Info: unable to get file lock, will retry …
Description: This message indicates that WLS can not get file lock because other process still holds the lock. W LS will try again before timeout.
Cause: This is an information-level message only.
Action: If WLS fails to start due to unable to get file lock, then lock files need to be removed manually before restart WLS.

The solution:

1. Delete the domain *.lok file
2. Remove the 1 edit.lok (Oracle/Middleware/user_projects/domains/idm_domain)
3. Remove the 2 config.lok (Oracle/Middleware/user_projects/domains/idm_domain/config/)
4. Remove the 3 AdminServer.lok (Oracle/Middleware/user_projects/domains/idm_domain/servers/AdminServer/tmprm AdminServer.lok)
5. Remove the 4 EmbeddedLDAP.lok (Oracle/Middleware/user_projects/domains/idm_domain/servers/AdminServer/data/ldap/ldapfilesrm EmbeddedLDAP.lok)
6. Restart the weblogic.

Note: In case the .lok file is unable to delete, stop the java.exe program from task manager and try again.

OBIEE file locations:

NodeManager. properties: C:\MW_HOME\wlserver_10.3\common\nodemanager

NQSConfig File: C:\MW_HOME\instances\instance1\config\OracleBIServerComponen\coreapplication_obis1

StartWebLogic/SetDomainEnv: C:\MW_HOME\user_projects\domains\bifoundation_domain\bin

Repository: C:\MW_HOME\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository

nqserver: C:\MW_HOME\instances\instance1\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1

sawlog: C:\MW_HOME\instances\instance1\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1

instanceconfig.xml: C:\MW_HOME\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1

tnsnames.ora:   C:\MW_HOME\Oracle_BI1\network\admin\sample