6/27/2016 DocumentDisplay

FusionApplicationsBIPublisher:TroubleshootingBIPublisherPerformanceandMemoryGuard
relatedissues(DocID2002290.1)

InthisDocument

Purpose
TroubleshootingSteps

1)ReportDesign
2)Errors
3)Investigate
SQLTimeout

Overview

Error

ReportMaxDataSize

Overview

Error

Resolution

MemoryCalculationforHTMLreports
MemoryCalculationforPDFreports
MemoryCalculationforXLSXreports(Excel)
HeapandtheEstimatedMemoryConsumedrelationship
CalculatingtheHeapSizeAfteraReportMaxDataSizeUpdate

4)Resolve

APPLIESTO:

OracleFusionApplicationToolkitVersion11.1.10.0.0andlater
OracleFusionApplicationToolkitCloudServiceVersion11.1.10.0.0andlater
Informationinthisdocumentappliestoanyplatform.

PURPOSE

Thisdocumentprovidestroubleshootingstepstoassistwiththediagnosisandtroubleshootingofreportgenerationfailures
triggeredbytheBIPublisherMemoryGuardperformancemonitor.

ThestandarddocumentationfortheBIPublisherMemoryGuardfeaturecanbefoundintheFusionMiddlewareAdministrators
GuideforOracleBusinessIntelligencePublisher

TROUBLESHOOTINGSTEPS

TheBIPublisherMemoryGuardisdesignedtopreventBIPublisherreportsfromconsumingexcessiveamountsofmemoryon
theBIServer.InthepastareportwhichconsumedexcessiveamountsofmemorycouldcausetheWeblogicServerhostingthe
BIDomaintoencounteranOutOfMemoryconditionwhichwouldinturncauseittoshutdownandrestart,triggeringanoutage
ofBIfunctionality.Oftentheuserrunningthereportwouldbeunawarethattheyhadtriggeredtheoutagebutrepeated
executionofthereportwouldresultinrepeatedoutagesandadverseimpactontheuserbase.AsaresulttheMemoryGuard
wasdevelopedtoimposerestrictionsontheamountofmemoryandsizeofdatathatareportcoulduseandtherebyprevent
theserepeatedoutagesoftheserver.

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=i4as399ga_57#aref_section22 1/8
6/27/2016 DocumentDisplay

Ifacustomreportisrepeatedlyfailingthenthereareanumberofstepswhichcanbetakentotryanddeterminewhetheror
nottheMemoryGuardispreventingitsexecution.

1)ReportDesign

MostreportswhichfailencounterMemoryGuardrestrictionsbecausetheyaregeneratinglargeamountsofXMLdatawhich
wouldrequireexcessiveamountsofmemorytoprocess.OftenthisexcessiveXMLgenerationandmemoryconsumptionstems
fromapoorlyunderstoodordesignedreportwhichisrunningacustomSQLqueryagainstthedatabase.Withthatinmindif
youfindthatareportyouarerunningisrepeatedlyfailingthenlooktotestwithreducedamountsofdatabyaddingfilteringto
thereport,ifitthencompletesthenitislikelythatyouhavealongrunningqueryorexcessivedatatoprocess.

PointsofNote:

i)ensurethatyouarenotrunning'blind'wildcardqueriesagainstdatabasetables.Thereisatemptationtoperformthis
typeofqueryfordatavalidationortoreviewthedatathatthetablescontainbutthiscanresultinverylargeamountsof
databeingretrieved.ExplicitlylisteachcolumntoberetrievedandusetheOracleEnterpriseRepositoryforFusion
Applicationsaguidetothetablestructure:https://fusionappsoer.oracle.com/oer/index.jsp

ii)ensurethatanycustomqueryisrestrictedtoamaximumof60columnsasdocumentedintheDataModellingGuide:

"..2.3.3.7SupportedColumnTypes
ColumnsofalltypesdisplayasobjectsintheDesignpane.Notethefollowingcolumnrestrictions:
Youcanselectnomorethan60columnsforeachquery..."

iii)ensurethatqueriesarenotsimplypulledfromtheOBTInqquery.logandcopiedintoaBIPublisherreport.Reviewthe
SQLbeingissuedandensurethatanysubqueriesarenecessaryandrequiredforthequerybeingissued

iv)ensurethatyoudonotsimplyjoinlargenumbersoftableswithoutrestriction.Variouscustomreportshavebeenseen
where>10tableshavebeenjoinedtogetherwithprimarykeyjoinsandnofiltering.Thiscanmeanthatverylarge
resultsetsaregenerated.

2)Errors

BIPublisherMemoryGuardtriggersanumberofdifferenttypesoferrormessagedependentonthespecificsofthescenario
encountered,anumberofthemorecommonlyseenhavebeenincludedbelowtoactasaguidetotheBIAuthorandUser:

Jul22,20145:00:59PMoracle.xdo.enterpriseScheduler.util.ProcessorUtillogException
WARNING:!!!!!!!BurstingJobProcessor.getReportData::::ERROR_GETTING_REPORT_DATA::
[INSTANCE_ID=adc00cfa.1406056167500]IOException:[INSTANCE_JOB_ID=1054]
oracle.xdo.dataengine.diagnostic.XMLSizeLimitException:XMLOutput(200446bytes)generatedexceedsspecifiedfile
sizelimit(200000bytes)..!!!!!!!
Pleasecontactsystemadministratortoincreasefilesizelimit.
oracle.xdo.XDOException:oracle.xdo.dataengine.diagnostic.XMLSizeLimitException:XMLOutput(200446bytes)generated
exceedsspecifiedfilesizelimit(200000bytes)..!!!!!!!
Pleasecontactsystemadministratortoincreasefilesizelimit.
atoracle.xdo.dataengine.XMLPGEN.processMergedDataSet(XMLPGEN.java:1652)
atoracle.xdo.dataengine.DataProcessor.processData(DataProcessor.java:376)

Jul22,20144:46:45PMoracle.xdo.servlet.XDOServletWARNING:javax.servlet.ServletException:oracle.xdo.XDOException:
oracle.xdo.dataengine.diagnostic.XMLSizeLimitException:XMLOutput(105801bytes)generatedexceedsspecifiedfile
sizelimit(100000bytes)..!!!!!!!
Pleasecontactsystemadministratortoincreasefilesizelimit

Jul22,20144:43:34PMoracle.xdo.online.ViewerIOWARNING:oracle.xdo.XDOException:oracle.xdo.XDOException:
oracle.xdo.XDOException:java.io.IOException:Memoryabovememorylimit:257426
atoracle.xdo.online.DataCache.getDataFile(DataCache.java:430)
atoracle.xdo.online.ViewerIO.createReportViewData(ViewerIO.java:981)

Erroroccurredonretrievingdataxml

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=i4as399ga_57#aref_section22 2/8
6/27/2016 DocumentDisplay
Reportdatasizeexceedsthemaximumlimit(524288000bytes).Stoppedprocessing.

OneormoreoftheerrormessageslistedabovemayappeartoanenduserrunningareportwhichencountersaMemory
Guardrestriction.

Amoredetailedexplanationofthepossibleerrormessagescanbefoundin
FusionApplications:BIPublisherMemoryGuard,associatedmessages:XMLOutputgeneratedexceedsspecifiedfilesizelimit,Filedoesnotbegin
with'%PDF',oracle.xdo.XDOException:java.io.IOException:Memoryabovememorylimit(DocID1914656.1)

3)Investigate

UponencounteringoneoftheaboveerrorstheBIAuthororUserneedstoinvestigatetherootcauseandtakeremedialaction.

Severalconfigurationparameterswereintroducedthatcanbesettokillreportsthatareeitherconsumingtoomuchmemory
ortakingtoolongonSQLexecution.AtthetimeofwritingthemostcommonlychangedMemoryGuardsettingsare:

1.SQLTimeoutthisconfigurationparametersetsthelongesttimeaSQLquerycanexecutebeforetimingout.The
defaultissetto10minutes(600seconds),whichshouldbelongenoughformostreports.
2.REPORT_MAX_DATA_SIZEthisconfigurationparametersetsthelargestamountofXMLdatapermittedfora
report.Thedefaultissetto500MBforoffline(scheduled)reportsand300MBforonlinereports,whichshouldbe
largeenoughformostreports.Thisdocumentdoesnotdistinguishbetweenthetwo,ascalculatingtheneededvalueis
thesame,andresettingthevalueisonthesamepage.Ifthereisadistinction,thenoneortheotherisexplicitly
mentioned.

Inthetablebelow,thedefaultconfigurationvaluesareshowalongwithvaluesthatareusedonalargeconfiguration.These
areshowntogiveanideaoftherangeofcurrentlyusedvalues:

ConfigurationParameterName DefaultValue LargeSyst

SQLTimeout 600seconds 20400secon
ONLINE_REPORT_MAX_DATA_SIZE 300MB 2000MB
OFFLINE_REPORT_MAX_DATA_SIZE 500MB 3000MB
Heap(Max) 6GB 16GB
BIMachineOVMmemory(Max) 24GB 73GB

SQLTimeout

Overview

TheSQLTimeoutwasaddedbecausemanyreportswereexecutingpoorlygeneratedSQL,whichresultedinmanystuck
threadswaitingfortheSQLtofinish.Thesituationworsenedwhenusersclicked'Submit'multipletimes,andasaresult,many
threadsweregettingstuck.Oncethenumberofstuckthreadsreachedtheconfiguredlimit(25onFAenvironments),
WebLogicServer(WLS)rebooteditself.WLSconsidersathreadstuckifthethreadhasnotexecutedanystatementsafter10
minutes,hencethedefaultSQLTimeoutvalueof10minutes.RaisingthisvaluehasthepotentialtocausetheWLStorebootif
25threadsgetstuckwaitingfortheirSQLqueriestofinishexecuting.Thissituationcanoccurifausersubmitsarequestto
viewareportthroughtheUI,andwhilethereportisprocessing,theusergetsimpatient,andclicksthe'Submit'buttonagain.
Eachoftherequestsusestwothreadsonetoexecutethequery,andanothertokilltheoriginalexecutingthreadifneeded.If
morethan13requestsaremade,theSQLexecutionistakesover10minutes,andtheSQLTimeouthasbeensetto20
minutes,theserverwillnoticethat26threadshavenotexecutedstatementswithinthe10minutethreshold,andthemanaged
serverwillberebooted.

Error

TheSQLTimeoutlimithasbeenhitwhenthelogfilecontainsthefollowingerrormessage:
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=i4as399ga_57#aref_section22 3/8
6/27/2016 DocumentDisplay

[20141006T17:21:38.816+00:00][bi_server1][ERROR][][oracle.xdo][tid:24][userId:19491][ecid:0051CGgVsax9Le73VJrIB800067p0003if,0:4][APP

SQLquerytimeexceedsthelimit(600sec).Stoppedprocessing.

***Reportpath=/Custom/Financials/GeneralLedgerSummarybySource.xdo
***DataModelpath=/Custom/Financials/XX_Report_DM1.xdm
]]

Resolution

Thereareseveralwaystoaddressthiserror,basedontheanswerstothefollowingquestions.

Isthiserrorhappeningononlyasinglereportoronmanyreports?

Ifonlyonasinglereport,thenchangetheSQLTimeoutonthedatamodel.

Ifthishappensformanydifferentreportsonmanydifferentdatamodels,thenchangethevalueforalldatamodels
throughtheinstancewideSQLTimeout.

IsthisanOracledeliveredreportoraCustomreport(lookattheReportpathintheerroroutput,andifCustomappearsinit,
thenit'saCustomreport)?

OracleReportRaiseaServiceRequestsotataninvestigationcanbeundertaken.Noneofthedeliveredreportsshould
takemorethan10minutestoexecute.IncreasetheSQLTimeoutvalueonthedatamodelforthisreport,sothatthe
customercangetpastthisissue.

CustomReportAdjustthereportparametersinordertodecreasetheamountofdatabeingretrievedandtakestepsto
tunethequery.

Whenupdatingthevaluetherecommendationistoincreasethevaluein10minuteincrements,untiltheerrorsgoaway.

ReportMaxDataSize

Overview

BIPublisherprocessinghappensinseveralmainsteps:

1.QuerythedatabaseandgenerateXMLfromtheResultSet
2.FormattheXMLDataintoanotheroutputformat
3.Deliverthefile

TheReportMaxDataSizeparametersetsthelimitthatthefirststepcantake,whengeneratingtheintermediateXMLdata
size.AtypicalreportwillquerythedatabaseandcomeupwithaResultSetofrows.Theserowsarethenprocessedoneata
time,andconvertedfromthetherowsintoXML.TheReportMaxDataSizeparameterlimitsthesizeoftheintermediateXML
filegenerated.Thecurrentdefaultvaluesare300MBforonline(submittedandviewedthroughtheUserInterface)and500
MBfortheoffline(scheduled)reports.ThesizeoftheXMLdatageneratedisdirectlyrelatedtotheamountofmemoryusedto
processthereport.So,thelargerthevalueofReportMaxDataSize,themorememorythatisneededtoprocessareportthat
returnsalargeamountofdata.

RaisingthisvaluecanresultinanOutOfMemoryException,iftheamountofmemoryneededtoprocessaparticularreportis
notavailableintheheapofthecurrentWLS.ThereareseveralfactorsthatcomeintoplaywhentryingtocalculatetheMax
XMLDataSize:

1.MaxConcurrentJobsTheconcurrentjobssetting(defaultissetto6)isthenumberofjobsthattheBIPjob
schedulerallowstorunatatimeforofflinereports.Ifmorethan6reportsaresubmitted,thereportsareputintoa
queue,sothatBIPonlyprocessestheconfiguredmaximumconcurrentnumberofjobsatonetime.
2.HeapThemaxheapsettingforthemanagedserver,bi_server1.ThecurrentdefaultforFABImanagedserveris6
gb.
3.InitialSteadyStateTheamountofmemoryconsumedbybi_server1afterstartup,andithasreachedsteadystate.
Thecurrentobservedvalueis700mb.

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=i4as399ga_57#aref_section22 4/8
6/27/2016 DocumentDisplay

4.MaxXMLDataSettingTheMaxXMLDataSizeSettingisthemaximumamountofmemoryasinglereportcan
allocateforasingleinvocation.ThecurrentdefaultforFAis500mb.
5.OutputFormatTheoutputformat(i.e.,pdf,xlsx,html,etc.)
6.EstimatedMemoryConsumedEstimatedamountofmemoryconsumedforaparticularXMLDataSizegivenan
OuputFormat

Error

TheReportMaxDataSizelimitisreachedwhenthelogfilecontainsthefollowingerrormessage:

[20141028T06:53:13.183+00:00][bi_server1][ERROR][][oracle.xdo][tid:30][userId:TKassana][ecid:0051bOMQXbt7a6Tvy8ADT00000ly000dJ8,0:3][

Reportdatasize(314631374bytes)exceedsthemaximumlimit(314572800bytes).Stoppedprocessing.[[
***Reportpath=/Custom/Financials/GeneralLedgerSummarybySource.xdo
***DataModelpath=/Custom/Financials/XX_Report_DM1.xdm
]]

Resolution

ThereisarelationshipbetweentheReportMaxDataSizeandtheheapontheJVMforthemanagedserver,bi_server1and
thefollowingformulasanalyzethisrelationship.

Hereareseveraltermsthatareusedinthecalculationsthatfollow:

ReportMaxDataSettingTheReportMaxDataSizeSettingisthemaximumamountofmemoryasinglereportcan
allocateforasingleinvocation.ThecurrentdefaultforFAis500mb.
OutputFormatTheoutputformat(i.e.,HTML,csv,pdf,xlsx,etc.).Assumptionisthatcsvwillconsumethesame
amountofmemoryasHTML,sincetheyarebothtext.
EstimatedMemoryConsumedEstimatedamountofmemoryconsumedforaparticularXMLDataSizegivenan
OutputFormat

MemoryCalculationforHTMLreports

HereistheformulatocalculatetheEstimatedMemoryConsumed,iftheOutputFormatofthereportisHTML:

EstimatedMemoryConsumed=(0.05*ReportMaxDataSettinginMB)+60MB

Forinstance,inthecaseforthedefaultReportMaxDataSettingis500MB,theestimatedamountofmemoryconsumedfora
HTMLoutputwouldbe:

EstimatedMemoryConsumed=(0.05*500MB)+60MB

=(25MB)+60MB

=85MBconsumed

MemoryCalculationforPDFreports

HereistheformulatocalculatetheEstimatedMemoryConsumed,iftheOutputFormatofthereportispdf:

EstimatedMemoryConsumed=(0.3*ReportMaxDataSettinginMB)+35MB

Forinstance,inthecaseforthedefaultReportMaxDataSettingis500MB,theestimatedamountofmemoryconsumedfora
pdfoutputwouldbe:

EstimatedMemoryConsumed=(0.3*500MB)+35MB

=(150MB)+35MB

=185MBconsumed

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=i4as399ga_57#aref_section22 5/8
6/27/2016 DocumentDisplay

MemoryCalculationforXLSXreports(Excel)

HereistheformulatocalculatetheEstimatedMemoryConsumed,iftheOutputFormatofthereportisxlsx:

EstimatedMemoryConsumed=(1.5*ReportMaxDataSettinginMB)+50MB

Forinstance,inthecaseforthedefaultReportMaxDataSettingis500MB,theestimatedamountofmemoryconsumedfora
xlsxoutputwouldbe:

EstimatedMemoryConsumed=(1.5*500MB)+50MB

=(750MB)+50MB

=800MBconsumed

Asyoucansee,theOutputFormatofthereporthasasignificantimpactonthememoryconsumedonthemanagedserver(85
MBversus800MB)whencomparinghtmlandExcel!

HeapandtheEstimatedMemoryConsumedrelationship

OncetheEstimatedMemoryConsumediscalculatedbasedontheOutputFormatandtheReportDataSize,wecanchecktosee
iftheheapislargeenoughtoprocessthereport.Toestimatethis,weneedtoaddseveralmorefactorsthataffectthe
calculation:

MaxConcurrentJobsTheconcurrentjobssetting(defaultissetto6),isthenumberofjobsthattheBIPjobscheduler
allowstorunatatime.IfmorethanMaxConcurrentJobsreportsaresubmittedatonce,thereportsareputintoaqueue,so
thatBIPwillonlybeprocessingthemaximumconcurrentnumberofjobsatonetime.

HeapThemaxheapsettingforthemanagedserver,bi_server1.ThecurrentdefaultforFAis6gb.

InitialSteadyStateTheamountofmemoryconsumedbybi_server1afterstartup,andithasreachedsteadystate.The
currentobservedvalueis800mb.

Hereistheformulatoseeiftheheapislargeenoughtoprocessaparticularreport:

Heap>=(EstimatedMemoryConsumed*MaxConcurrentJobs)+InitialSteadyState

SubstitutingthecurrentdefaultvaluesusedinFAenvironments,wecandetermineifaparticularreportwillrunsafely.Inthe
aboveformula,interpretthe"?>="as"istheheapgreaterthanorequalto".ThereasoningbehindthisformulaisthatHeap
needstobelargerthantheamountofmemoryavailabletoBIPforprocessingtheEstimatedMemoryConsumedforone
report,timesmaxnumberofconcurrentreports,afteraddinginthesteadystatememoryusedbytheserver.

ForanHTMLoutputreport:

HeapDefaultfleetsettingis6gb
EstimatedMemoryConsumedforHTMLfordefaultfleetsettingof500mbdatasize=85MB(seecalculat
MaxConcurrentJobsDefaultfleetsettingis6
InitialSteadyStateEmpiriciallydeterminedvalueis800mb

?
6GB>=(85MB*6)+800MB)
6GB>=1310MB

Since6GBismuchlargerthan1310MB,theheapisabletorunthisreportsafely.However,iftheoutputformatischanged
toExcel,adifferentoutcomecanbeseen.

Foranxlsx(Excel)outputreport:

HeapDefaultfleetsettingis6gb
EstimatedMemoryConsumedforxlsxfordefaultfleetsettingof500mbdatasize=800MB(seecalcula

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=i4as399ga_57#aref_section22 6/8
6/27/2016 DocumentDisplay
MaxConcurrentJobsDefaultfleetsettingis6
InitialSteadyStateEmpiriciallydeterminedvalueis800mb

?
6GB>=(800MB*6)+800MB)
6GB>=5600MB

6GBislargerthan5600MB,butonlyslightlyandtheenvironmentrunstheriskofrunningoutofmemorywhenprocessing
Excelreports.

However,iftheusecaseisthattheparticularreportthatishittingthelimitisnotrunconcurrently(i.e.,onlyasingleuserruns
thereportatatime),thentheMaxMemorylimitcouldbeincreasedhigherwithoutincreasingtheheap.Thereasonisthat
otherreportscanruninparallel,butifthereisonlyoneinstanceofthelargereportrunning,thenthereshouldbeenoughheap
tosupportit.

IfacustomerisrunninglargereportsandisreceivingtheReportMaxDataSizelimiterror,runthecalculationsaboveandseeif
theheapislargeenoughtosupporttheincreasedlimit.IncreasingtheDataSizelimitcouldrequiremoreheapspace,based
ontheresults.

CalculatingtheHeapSizeAfteraReportMaxDataSizeUpdate

BeforeincreasingtheReportMaxDataSize,theheapsizeneededtosupporttheincreasedReportMaxDataSizeneedstobe
calculated.IftheReportMaxDataSizeisincreasedwithoutverifyingthattheheapcanaccommodatethenewvalue,an
OutOfMemoryExceptioncanresultontheBImanagedserver.

Afterusingtheformulasabove,boththeEstimatedMemoryConsumedvalueusedinconjunctionwiththecustomer'susecase
areusedtocalculatethenewheapsizeneededtosupportthereport.Itisimportanttokeepinmindtheusecase,asthishas
alargeimpactonthetotalamountofmemoryneededfortheheap.Notethatitisthesameformulashownabove,butinstead
ofusingtheheapvalueforchecking,weusethecalculatedheapvaluetoestimatethenewheapsize.

Willmultipleinstancesofthereportberunconcurrently?

Yesifmultipleinstancesofthereportwillberunconcurrently,thenretrievetheconcurrentjobvalue,
MaxConcurrentJobs,fromtheBIPJobScheduler.MultiplythatvaluewiththeEstimatedMemoryConsumedvalue,since
therecanbeatmostMaxConcurrentJobsnumberofreportsrunningatthesametime.AddtheInitialSteadyStatevalue,
asthemanagedserverusesthatamountofheaptostartupandgetintoasteadystate(readytoprocessreports),and
thesumistheminimumheapsizeneededforthemanagedserver.

Forinstance:

EstimatedMemoryConsumed=750GB
InitialSteadyState=800MB
MaxConcurrentJobs=10
CurrentMaxHeap=6GB

HeapNeeded=(EstimatedMemoryConsumed*MaxCurrentJobs)+InitialSteadState
=(750MB*10)+800MB
=7500MB+800MB
=8300MB

Inthescenarioabove,theheapneededis8300MB,andthecurrentheapsettingof6GBistoolow,andwouldrun
theriskofanOutOfMemoryException.Thecustomer'sheapwillneedtobeincreasedtoatleast8300MBinorder
toaccommodatetheincreasedReportMaxDataSize.

Noiftherewillonlybeasingleinstanceofthereportrunatatime,thenaddtheInitialSteadyStatetothe
EstimatedMemoryConsumed,andthesumistheminimumtheheapsizeneededforthemanagedserver.

ItisimportanttoverifythattheBIOVMhasenoughfreememoryfreetosupporttheadditionalmemoryforthenewheapsize.
IftheadditionalmemoryneededrequiresmorememorytobeaddedtotheBIOVM,andthenewmemoryconfigurationfor
theBIOVMisabovetheMaxfortheOVM,thentheDom0fortheOVM,hastobecheckedforavailablememory.Allocating

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=i4as399ga_57#aref_section22 7/8
6/27/2016 DocumentDisplay

morememorytotheBIOVMabovetheMaxrequiresarebootoftheBIOVM,whichmeansanoutageforthedurationofthe
reboot.

4)Resolve

Inordertoresolvethebehaviouranumberofavenuesareopentotheuser:

Ifthereportisatthedesignstagestepscanbetakentoreviewthedatamodelandestablishifactionscanbetakento
reducetheamountofdatabeingreturned.Columnscanbetruncatedfordisplayinthereport,checksmadetoestablish
ifcolumnscanberetrievedfromalternatelocations,andareviewmadetoestablishifgrouping,sorting,etccanbe
performedwithinthedatamodeltoreducetheamountofdatabeingsentbeforeanycalculationsareperformed.
Ifthefullsetofdataisrequiredthentheeffortscanbemadetorunthereportasascheduledjobratherthan
synchronouslyfromtheCatalog.Theexpectationisthatreportsrunsynchronouslyareexpectedtoreturninarelatively
shortperiodoftimeastheywouldcausetheuserssessiontohangwhilstthereportisgenerating,thereforetheywould
alsobeexpectedtohaveasmalldatasettoprocess.Ifalargedatasetistobeprocessedthenschedulethereportin
thiswayensuringthatonlytheXML_DATA_SIZE_LIMITisbeingapplied.
AsafinaloptiondiscussionscouldbehadwiththeBIAdministratortoestablishifchangescouldbemadetothe
MemoryGuardparametersinordertoallowthereporttocomplete.Thisshouldbeconsideredalastresortas
increasinganyoftheMemoryGuardparametersettingswillincreasethescopeforotherreportsanduserstorunlarger
reportsandultimatelycouldleadtoOutOfMemoryscenariosandBIDomainoutagesifnotproperlymanaged.

TheparametersareavailablethroughtheBIPublisher>Administration>RuntimeConfiguration>Properties:

Didn'tfindwhatyouarelookingfor?

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=i4as399ga_57#aref_section22 8/8