This error is due to number of records exceeded in Cube.
The error can be resolved by following:
1. open instanceconfig.xml , which is located to <oracle_home>:\OracleBIData\web\config\instanceconfig.xml. It will be like:
<?xml version="1.0" encoding="utf-8"?>
<WebConfig>
<ServerInstance>
<DSN>AnalyticsWeb</DSN>
<CatalogPath>C:/OracleBIData/web/catalog/TESTCATALOG</CatalogPath>
<Alerts>
<ScheduleServer>localhost</ScheduleServer>
</Alerts>
<AdvancedReporting>
<ReportingEngine>XmlP</ReportingEngine>
<Volume>XmlP</Volume>
<ServerURL>http://localhost:9704/xmlpserver/services/XMLPService</ServerURL>
<WebURL>http://localhost:9704/xmlpserver</WebURL>
<AdminURL>http://localhost:9704/xmlpserver/servlet/admin</AdminURL>
<AdminCredentialAlias>bipublisheradmin</AdminCredentialAlias>
</AdvancedReporting>
<JavaHome>C:\Program Files\Java\jdk1.6.0_01</JavaHome>
<BIforOfficeURL>client/OracleBIOffice.exe</BIforOfficeURL>
</ServerInstance>
</WebConfig>
2. Modify instanceconfig.xml and add following:
<CubeMaxRecords>500000</CubeMaxRecords>
<CubeMaxPopulatedCells>500000</CubeMaxPopulatedCells>
Here, 500000 is count according to the data to be displayed.
now, instance config will be like:
<?xml version="1.0" encoding="utf-8"?>
<WebConfig>
<ServerInstance>
<DSN>AnalyticsWeb</DSN>
<CatalogPath>C:/OracleBIData/web/catalog/TESTCATALOG</CatalogPath>
<Alerts>
<ScheduleServer>localhost</ScheduleServer>
</Alerts>
<AdvancedReporting>
<ReportingEngine>XmlP</ReportingEngine>
<Volume>XmlP</Volume>
<ServerURL>http://localhost:9704/xmlpserver/services/XMLPService</ServerURL>
<WebURL>http://localhost:9704/xmlpserver</WebURL>
<AdminURL>http://localhost:9704/xmlpserver/servlet/admin</AdminURL>
<AdminCredentialAlias>bipublisheradmin</AdminCredentialAlias>
</AdvancedReporting>
<JavaHome>C:\Program Files\Java\jdk1.6.0_01</JavaHome>
<BIforOfficeURL>client/OracleBIOffice.exe</BIforOfficeURL>
<CubeMaxRecords>500000</CubeMaxRecords>
<CubeMaxPopulatedCells>500000</CubeMaxPopulatedCells>
</ServerInstance>
</WebConfig>
3. Re-start the Presentation service and log-in to the application.
Cheers,
Neeraj
The error can be resolved by following:
1. open instanceconfig.xml , which is located to <oracle_home>:\OracleBIData\web\config\instanceconfig.xml. It will be like:
<?xml version="1.0" encoding="utf-8"?>
<WebConfig>
<ServerInstance>
<DSN>AnalyticsWeb</DSN>
<CatalogPath>C:/OracleBIData/web/catalog/TESTCATALOG</CatalogPath>
<Alerts>
<ScheduleServer>localhost</ScheduleServer>
</Alerts>
<AdvancedReporting>
<ReportingEngine>XmlP</ReportingEngine>
<Volume>XmlP</Volume>
<ServerURL>http://localhost:9704/xmlpserver/services/XMLPService</ServerURL>
<WebURL>http://localhost:9704/xmlpserver</WebURL>
<AdminURL>http://localhost:9704/xmlpserver/servlet/admin</AdminURL>
<AdminCredentialAlias>bipublisheradmin</AdminCredentialAlias>
</AdvancedReporting>
<JavaHome>C:\Program Files\Java\jdk1.6.0_01</JavaHome>
<BIforOfficeURL>client/OracleBIOffice.exe</BIforOfficeURL>
</ServerInstance>
</WebConfig>
2. Modify instanceconfig.xml and add following:
<CubeMaxRecords>500000</CubeMaxRecords>
<CubeMaxPopulatedCells>500000</CubeMaxPopulatedCells>
Here, 500000 is count according to the data to be displayed.
now, instance config will be like:
<?xml version="1.0" encoding="utf-8"?>
<WebConfig>
<ServerInstance>
<DSN>AnalyticsWeb</DSN>
<CatalogPath>C:/OracleBIData/web/catalog/TESTCATALOG</CatalogPath>
<Alerts>
<ScheduleServer>localhost</ScheduleServer>
</Alerts>
<AdvancedReporting>
<ReportingEngine>XmlP</ReportingEngine>
<Volume>XmlP</Volume>
<ServerURL>http://localhost:9704/xmlpserver/services/XMLPService</ServerURL>
<WebURL>http://localhost:9704/xmlpserver</WebURL>
<AdminURL>http://localhost:9704/xmlpserver/servlet/admin</AdminURL>
<AdminCredentialAlias>bipublisheradmin</AdminCredentialAlias>
</AdvancedReporting>
<JavaHome>C:\Program Files\Java\jdk1.6.0_01</JavaHome>
<BIforOfficeURL>client/OracleBIOffice.exe</BIforOfficeURL>
<CubeMaxRecords>500000</CubeMaxRecords>
<CubeMaxPopulatedCells>500000</CubeMaxPopulatedCells>
</ServerInstance>
</WebConfig>
3. Re-start the Presentation service and log-in to the application.
Cheers,
Neeraj
No comments:
Post a Comment