11/30/2016 NewWebIfeatureinBI4.

2ParallelQueriesSAPBlogs

GetStarted

Solutions Support Training Community Developer

Partner About

Community / Blogs

NewWebIfeatureinBI4.2
ParallelQueries
January22,2016 | 542Views |
RobertTwigg
morebythisauthor

SBOPWeb/DesktopIntelligence(client/server)

Solution | analytics | bi42 | BusinessIntelligence | businessintelligence

(businessobjects) | businessobjects | dps | intelligence | parallel | paralleldataproviders | parallelque
businessobjectswebintelligence | sapbusinessobjectswebintelligence42 | webintelligence |
tricks | webi42 | webintelligence

share
0 share
0 tweet share

Follow

IworkontheSAPWebIntelligence(Webi)Supportteam.Iwantto
highlightoneofthenewfeaturesthatwillbeintroducedforWebIinSAP
BusinessObjectsBusinessIntelligencePla orm4.2(BI4.2)calledParallel
Queries.Thisallowsforparallelqueryexecu ontobeperformedwhen
refreshingWebIdocumentswithmul pledataproviders.

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 1/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

PriortoBI4.2:Eachdataprovider(query)inaWebireportwasrun
sequentially(whenthefirstqueryfinishedexecuting,thesecond
wouldrun,andsoon).

StartinginBI4.2:Parallelqueryexecutionisenabledbydefaultfor
WebIdocumentsthathavemultipledataproviders.

Thereisnoparallelactivityattherefreshpreparation(i.e.query
scriptgeneration,resolutionofcontexts,andprompts)
Parallelactivitiesoccuronthedatabaseattheexecutionand
datafetchpartoftherefreshprocess.
Parallelquerieswillnotberunfordependentdataproviders.

Parallelqueriesaresupportedforthefollowingdataprovider
types:

Dataprovidersthatarebasedonunvandunxuniverses.
DataprovidersbasedonSAPHANADirectAccess.
DataprovidersthatarebasedonFreehandSQLandText
Files.

SupportedWebIntelligenceclients:

WebIRESTSDK
Scheduler
WebIRichClient
WebIHTMLandAppletinterfaces.

ThefollowingscreenshotshowswhathappensbeforeBI4.2andin
BI4.2:

ParallelQuerySettingsattheWebIlevel:

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 2/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

Themaximumnumberofconcurrentrefreshjobsissetinthe
WebIContainer_ClientDescriptor.xmlfilefortheWebiRich
Client.
Themaximumnumberofconcurrentrefreshjobsissetinthe
WebIContainer_ServerDescriptor.xmlfileforWebIrunningon
theserver(throughBILaunchpad)
ForadefaultinstallationlocationonWindows,thelocationof
theaboveXMLfilesisasfollows:
C:\ProgramFiles(x86)\SAPBusinessObjects\SAP
BusinessObjectsEnterpriseXI4.0\win32_x86\config
Thepropertythatissetiscalled
WebiParamMaxConcurrentRefreshJobs.
Bydefault,theMaximumConcurrentRefreshJobsissetto64.
Thiscanbesettoavaluethatyoufindworkswellforyour
system.Ifthevalueissetto0,thentheparalleldatarefreshis
disabledalltogether.

ThefollowingshowstheWebiParamMaxConcurrentRefreshJobs
parameterintheDescriptorXMLfile:

Thefollowingdescribesthebehavioratthedatabase
connectionlevelrelatingtoparallelqueries:

Therecanbenomorethanfourconcurrentqueriesrunningon
thesamerelationalconnection.
Therecanbenomorethanoneconcurrentqueryonthesame
OLAPconnectionortextfile.
AsofBI4.2SP01,parallelquerysettingcannotbechangedfor
eachdatabaseconnection.Thesettingcurrentlyappliesto
everyconnection.

AsummaryofthelimitationsinSAPBI4.2areasfollows:

Itisnotpossibletorunparallelqueriesondataprovidersbased
onDirectAccesstoBExqueries(BICS).
Itisnotpossibletorunparallelqueriesondataprovidersbased
onAnalysisViews.
Itisnotpossibletorunparallelqueriesondataprovidersbased
onExcelfiles.

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 3/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

Itisnotpossibletochangeparallelquerysettingforeach
databaseconnection.Ibelievethatthiswillbelookedatbeing
incorporatedintoasupportpacklaterthanBI4.2SP01.

Exampleofthelogfileanalysisofaparallelqueryexample:

Inthisexample,aWebireportwasrefreshedintheWebiRich
Client.
TheWebiParamMaxConcurrentRefreshJobsparameterwasset
to64intheWebIContainer_ClientDescriptor.xmlfile.
Thewebireportisrefreshedwith4dataprovidersthatallpoint
tothesamerelationalconnection.
Sincethereare4queriesthatareallpointingtothesame
connectionwhichislessthanorequaltothelimitof4parallel
queriesperconnectionandsincethe
WebiParamMaxConcurrentRefreshJobsparameterissettoa
numberof64andnootherqueriesarerunningatthesame
timeasmytest,thequeriesshouldallberuninparallel.
WebiRichClientloggingwasenabledwithsap_trace_level=
trace_debugwhenrefreshingthereportwiththe4queries
runninginparallel.
The.glflogfilewassaved.

LogFileAnalysis:

Toanalyzethelogfiles,IusedtheFlexiLogReader.Thislogreader
canbeusedforanalysisofBI.glflogfiles.TheFlexiLogReadercan
beretrievedfromthefollowinglink:

FlexibleLogReader

AnalysisSteps:

1.OpentheFlexiLogReaderbylaunchingtheFlexiLogReader64.exe
file.

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 4/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

2.SelecttheWebiRichClient.glflogfilethatwascreatedwhen
loggingwasturnedonwhenrefreshingthereportwith4queries
runninginparallel.

3.Specifythedefaultconfiguration(PLUGIN:BI4.xGLFLogParsing
andEndtoEndAnalysis(v1.2.0).

4.Specifytoloadallfilesthatareinthedirectoryofthefilethatyou
justselected.Inthiscase,weonlyhaveone.glflogfile,butifthere
https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 5/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

weremore,byselectingthisoption,allofthefilesinthecurrent
directorywouldbechosen.

5.Whenthelogfilesareloaded,noticethatoneofthewaysthatthe
logfilesaredisplayedisbyServerName/PID/TID.Thismeansthat
thelogscanbebrokenoutbyServerName=WebRichClient,
ProcessID(InthisanalysisthereisonlyoneprocessID),andThread
ID(therearemanythreads).Theadvantageofthisforanalyzing
refreshesofparallelqueriesisthattherewillbeonethreadthat
managesthecreationofalloftherefreshes,andafurtherthreadwill
bespawnedforeachoftheindividualrefreshes.

6.Tofindthelinesofcodethatarerelatedtotheparallelrefresh
process,findallofthelinescontainingthetag[//R].Todothisinthe
FlexiLogReader,selectSearchSearchWindowtobringupthe
searchwindow.

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 6/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

Thesearchtermshouldbeaddedasatagsothatwecanfilterthe
logstoonlyseetheentriesthatincludethelinesthathavethe[//R]
entry.

NowensurethatyouonlychecktheSearchTerms[//R]taganddont
checkanyoftheotherones.Afterthat,selectShowOnlyLogEntries
LinkedToSelectedTags.

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 7/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

Now,showanextracolumnthatreferstotheThreadID.

Firstoff,findoutwhatthreadIDisassociatedwiththefirstrowthat
wasreturnedinthe[//R]search.

Fromtheabove,wecanseethatthethreadIDthatisassociatedwith
thatfirstrowis9028.

Now,addtheThreadIDcolumntothecolumnsthatareshownin
thetracesummary.Todothat,selectthefirstrow,selectView,and
selectChooseColumnsToShow.

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 8/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

IntheDefineVisibleColumnsscreen,checkthe9028column
whichstandsforthethreadIDcolumnandthenselectOK.

TheresultisthatwenowhaveColumn3showingwhichisthe
Timestamp,Column12showingwhichistheThreadID,and
Column36showingwhichistheText.

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 9/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

7.Bylookingatthelogsthatarefilteredby[//R],wecanseethatthereare
thefollowing5differentthreads:

9028ThisisthethreadIDofthemainthreadthatmanagesthe
refreshesofthe4differentdataprovidersthatarerefreshingin
parallel.

11212Thisisthethreadfortherefreshofthefirstdataprovider
(DP0).

11208Thisisthethreadfortherefreshoftheseconddata
provider(DP1).

11776Thisisthethreadfortherefreshofthethirddataprovider
(DP2).

12028Thisisthethreadfortherefreshofthefourthdata
provider(DP3).

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 10/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

8.Inthemainthread(threadID=9028inthiscase),thefollowing
showsthestartandfinishofeachofthequeriesthatarebeingrunin
parallelasseparatethreads.

9.InFlexiLogReader,wecantakethethreadIDofoneofthethreads
foroneofthequeryrefreshesandfilterbasedonthatthreadID.So,
forexample,ifwetakethethreadIDofthefirstquerythatisrefreshed
(threadID=11212)andfilterbasedonthatthreadID,weseethe
following(asshowninthebelowscreenshot).Wewillleavethe[//R]
searchtermselectedsothatinthesummaryscreen,wewillseethe
logsforthreadID=11212aswellasthelogsforthe[//R]search
term.ByfilteringonthethreadID,youcanseealloftheactivitiesthat
wentonduringtherefreshprocess.Youcanseewhenthethread
starts,whichqueryitisreferringto,andwhenthethreadend(when
therefreshisfinishedforthatquery).
https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 11/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

Youcananalyzetheotherqueryrefreshesintheotherthreadsusing
thesameprocessasshownabove.

Summary:

IhopethatthisbloghashighlightedtheParallelQueriesfeaturethat
willbeavailableinBI4.2includingthedataprovidersthatitis
supportedon,howtoconfigureit,howitshouldleadtoquicker
refreshtimes,andhowthelogfilescanbeexaminedeffectivelyusing
theFlexiLogReader.Itlookslikethiswillbeagreatfeature!

AlertModerator

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 12/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

29Comments
YoumustbeLoggedontocommentorreplytoapost.

TedUeda

January22,2016at11:28pm

Kudos!Averydetailedblogthatdescribeshowtotroubleshootoneofthe
mostimpactfulnewfeatureofWebIntelligencewith4.2!
Regards,
TedUeda

SateeshKumar

January23,2016at10:40pm

HIRobert,
Oneofawaitingfeatures.verywellexplained.
DoyouknowwhythisfeatureisnotextendedforDirectAccesstoBExqueries
(BICS)?

Itismentionedthat,
TherecanbenomorethanoneconcurrentqueryonthesameOLAP
connectionortextfile.

so,willthisbeapplicableifweusemultipleOLAPconnectionspointingto
sameBW?
Thankyouverymuchforinformation

HenryBanks

January25,2016at9:40am

Hi,
WebiparallelqueriesforBICSOLAPisplannedforafutureSP
ontheBI4.2codeline.weareaimingforSP03butthisisinthe
planningstageandcouldbedelayed.

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 13/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

Regards,
H

SateeshKumar

January25,2016at9:52pm

ThankyouHenryforheadsup

PaoloMagnoli

February11,2016at11:27am

Hi,
anyplansforparallelpromptsorLOVvalues
retrieval?
Thanksinadvance

RobertTwigg Postauthor

February15,2016at5:15pm

Iamnotawareif/whenparallel
promptsofLOVvaluesretrievalis
plannedfor.

BDABICCTeam

September16,2016at6:58am

Hi,
AsdirectedaboveIdidchangetheparameterfrom
64to0aswewanttodisablethefeatureat
present,howeverevenafterrestartingSIAIstillsee
thatinWEBIServerMetricstheparameterstill
reflectsas64.
Isisaknownissueoritcanbeignored?
Regards,
Nachiket
https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 14/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

JasonEverly

January25,2016at1:45pm

GreatjobRobert!Veryhelpfulandinsightful.

JonathanBrown

January27,2016at12:59am

VerywelldoneRobert!Detailedasusualandgivessomegreat,practical
tipsonhowtousethenewlogreadertoo!
+++

ShubhaRadhakrishnan

May18,2016at8:01am

Veryinformativearticle.
Hasanyonehadissuesintheirenvironmentwiththedefaultvalueof64
WebiParamMaxConcurrentRefreshJobs?Wehaveawebireportwith14
dataprovidersandatleast10oftheseusethesamerelationaldatabase
connection.Thereportisscheduledtorunevery5minutes.Wehavenoticed
thattheschedulefailsintermittentlywithprocessDPCommandsExerrors.
Thewebiprocessingserverscrasheverytimetheschedulerunsirrespective
oftheoutcomeofthescheduleexecution.Wedisabledtheparalleldata
providerrefreshbysettingtheWebiParamMaxConcurrentRefreshJobsto0.
Theschedulerunswithouterrorandnowebiprocessingservercrashes
observed.
AnothertestwastoincreasetheWebiParamMaxConcurrentRefreshJobs
fromdefaultvalue64to84(arandomnumber),thissortofcontainedthe
issueinTestenvironmentbutdoesntseemtobeworkingintheDev
environment.
Wehave8cpucores,64gbram,windowsserver2012r264bitOSrunning
SAPBI4.2SP1Patchlevel2.Howdowedeterminethecorrectvalueforthe

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 15/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

WebiParamMaxConcurrentRefreshJobsparameter?Arethereanybest
practiceguidelinesrecommendedbySAP?
Thanks,
Shubha

HenryBanks

May18,2016at2:25pm

Hi,
pleaseworkwithtechnicalsupporttotroubleshootyourissue.
thepinchhereisthatyouarerunningaversionwhichwasused
duringtherampupprogramONLY.
theproductwentGAwithSP02sothatswherefixesare
portedtogoingforward..notSP01(whichisntmaintained
beyondtheprereleaseprogram)
Regards,
H

ShubhaRadhakrishnan

May19,2016at3:00am

HiHenry,
IvealreadyloggedaticketwithSAPSupportandin
theirresponsetheygavemealinktothisSCN
article. Justwonderingifthereisawayto
measuretheconsumptionofthe
WebiParamMaxConcurrentRefreshJobsparameter
usingtheWebiAdminTool?
IvepostedthesamequestionstoSAPSupportas
well.
Wevebeentoldthatalotofbugshavebeenfixed
intheGAreleasebutupgradingtotheGArelease
meansalotofplanning,packingofclienttools,
releasemanagement,itsaverytimeconsuming
taskforourorganisation.Sowellhavetoworkwith
therampupversionfornow.
Regards,
Shubha

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 16/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

DeepuReddy

May20,2016at9:32pm

ThanksRobert!
WehaveaWEBIReportwith10+DataProvidersallpointingto1Universe
with1RelationalConnection.
Only4queriesarehittingDBatapointintime.Imeanonly4Queriesare
runninginParallel.
IreachedouttoSAPSupportandtheyrefertothisblogandconcludedthat
only4QueriesruninParallelatMax.
IalsotriedbyupdatingWebiParamMaxConcurrentRefreshJobsparameter=128.
However0QueriesarerunninginParallel.

WeareonSAPBI4.2SP02.Cananyoneconfirmthatwecannotrunmore
than4ParallelQueriesinParallelinWEBI4.2onaSingleRelational
Connectionatatime.Ourgoalistohaveatleast8Queries/DataProviders
toruninParallel.
Thanks,
DEEPU.

RobertTwigg Postauthor

May20,2016at11:26pm

HelloDeepu.
Myunderstandingisthatthemaximumnumberofqueriesthat
canberuninparallelonthesamerelationalconnectionis4.
So,ifyouareseeingthatyouareonlyabletorun4queriesin
parallelagainstoneofyourconnections,thenthatwouldbe
correct.
Bestregards.
Robert

AjayGupta

May24,2016at1:58am

Robert,

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 17/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

Anyplanstoallowmorequeriestorunin
ParallelinBI4.2w/SP3?Anywaytocustomize
somesortofXMLfiletogetsupportformore
queries?
Anyfurtherdetailswouldbeappreciated.
Ajay

KashifAnsari

May24,2016at9:00am

HiRobert,
Thissettingisperconnectionperreportoronlyper
connection?WhatImeanisifwehaveareport
whichisalreadyrefreshingwith4paralleljobsand
someonefiresadifferentreportonthesame
relationalconnection,allthejobsonthenewreport
willhavetowaittillthetimeslotsarefreedbythe
1streport?

NirajParihar

May30,2016at5:02am

Interesting!!!

RajeshSinha

June16,2016at8:37pm

Welldocumentedandexplained,thanksRobert.

NathanTruhan

July20,2016at9:42pm

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 18/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

Haveacoupleusagequestions
Todisableparallelqueries,wejustconfigurethatconcurrentvalueto0inthe
xmlfileandrestarttheSIA,right?
Also,
Ifthethreadvalueis64threads,andthemaxforaconcurrentqueryis4
thenwecanconceptuallyrun16reportsthateachhad4parallelqueriesand
anythingafterwouldbequeueduntilthreadsfreeup.Iftherewasamixof
reportsandqueriesthenitcantotal64concurrentqueriesatonetimeto
varioussources,even64reportswith1queryeach.
Ifthisisdisabled,setto0,wouldreportsrunthesamewayastheydidin4.1
whereeachreportcanrunindependentandthequeriesareexecutedoneat
atime,butatsametime,orwouldtheyallbequeuedsuchthatifthereare
16reportsrunningonly1queryofthose16isrunningand15arequeued?
Finally,istheParametersettinginthexmlfilesetattheNode(SIA)level,or
isitaperwebiprocess?
Thanksinadvance,
Nathan

RobertTwigg Postauthor

July20,2016at11:09pm

HelloNathan.
Youasked:Todisableparallelqueries,wejustconfigurethat
concurrentvalueto0inthexmlfileandrestarttheSIA,right?
Answer:Correct.OrfromtheWebiRichClient,youwouldset
theWebiParamMaxConcurrentRefreshJobsparameterto0and
therestarttheWebiRichClient.
Youasked:Ifthethreadvalueis64threads,andthemaxfora
concurrentqueryis4thenwecanconceptuallyrun16reports
thateachhad4parallelqueriesandanythingafterwouldbe
queueduntilthreadsfreeup.Iftherewasamixofreportsand
queriesthenitcantotal64concurrentqueriesatonetimeto
varioussources,even64reportswith1queryeach.
Answer:Themaximumnumberofqueriesthatcanberunin
parellelis4perCONNECTION(notreport).So,ifthe16Webi
reportswereeachrunningbasedonadifferentconnection,then
conceptuallyifeachhad4queriesrunning(basedonthissame
connection),thentheycoukdallruninparallelandanything
afterwouldbequeueduntilthreadsfreedup.Thekeyisthat

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 19/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

themaximumis4pereachconnection.So,conceptuiallyyou
couldhave64reportsthateachhad1queryrunningaslongas
youhad16connectionswith4reportsbasedonone
connection,thenext4reportsbasedonanotherconnection,
etc.
Youasked:Ifthisisdisabled,setto0,wouldreportsrunthe
samewayastheydidin4.1whereeachreportcanrun
independentandthequeriesareexecutedoneatatime,butat
sametime,orwouldtheyallbequeuedsuchthatifthereare16
reportsrunningonly1queryofthose16isrunningand15are
queued?
Answer:Myunderstandingisthatifthisisdiasabled(setto0),
theWebireportswouldrunthesamewaythattheydidinBI4.1
whereeachreportcanrunindependentandthequeriesare
executedoneatatime,butatthesametime.
Youasked:IstheParametersettinginthexmlfilesetatthe
Node(SIA)level,orisitaperwebiprocess?
Answer:Thisissetattheentiresystemlevelnotforeach
WebiProcessingServer.
IfyoufindthatifanyofwhatIhavementionedaboveiscontrary
towhatyouareseeing,thenIwouldsuggestthatyoucreatean
incidentwiththeWebiSupportteambecausewhatIhave
mentionedaboveiswhatmyunderstandingisofhowthis
behaves.
Ihopethatthishelps.
Bestregards.
Robert

TARANRAI

July21,2016at6:22pm

GreatjobRob.
YourbloghelpedmealotinexplainingParallelQueryProcessingtoa
customer.
Keepupthegoodwork
Regards,
TaranRai

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 20/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

E.Ocula

September16,2016at6:21am

HiRobert.InBI4.2SP3,onecanchangethenumberofparallelqueriesalso
inCMC(WebIntelligenceProcessingServer).Whatistherelationbetweenthe
settingsintheXMLfileandwhatisvisibleinCMC?
WehavechangedthesettingintheXMLfilebutevenafteraSIArestart,the
changeinsettingisnotreflectedinCMC.
Canyoupleaseexplain?
Eddy

HenryBanks

September16,2016at8:23am

Hi,theCMCsettingisthewayanadminwouldchangeitusing
theInterface,whereaseditingtheconfigfileistheglobal
override?(iwouldntexpectittoreflectinCMCeither)

KeithFisher

October4,2016at12:40pm

Hi,
ImfacinganissuethatIthinkcouldberelatedtothisparallelprocessing:
AclientIworkforhasanew4.2DP03system,withallcontenthavingbeen
migratedfroma3.1SP5system.Therearealoadofreportsthatmakeuse
oftheresultfromanotherqueryfunctionalityinthequeryfiltersmorethan
onceperreport.Theyallrunfineonthe3.1system.
Whenrunningthesereports,9outof10timestheywillfailwithanMSSQL
ODBCerrorstating:Thefollowingdatabaseerroroccurred:[Microsoft]
[ODBCSQLServerDriver][SQLServer]Incorrectsyntaxnear,..
AsthesesamelinkedqueriesoftencontaincustomSQLisitpossiblethatthe
BOBJplatformisnotspottingthatthequeriesaredependentoneachother
andneedtoberuninsequencethenwhenaquerythatcontainscode
suchas:stepareferral.ICSReferralIDIN@dpvalue(N,DP2.DO459)isrun,
itfallsoveratthe,becausethesecondDPisnotwhereitshouldbe?The

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 21/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

onetimeitdoesrunsuccessfullycouldbebecausethequeriesjust
happenedtorunintherightorder?
IfyouthinkthisislikelywhatshouldIlookforinthelogsandhowcanIwork
arounditcanIsetthenumberofconcurrentqueriesto1intheWebi
ProcessingServers?
thanks
Keith

KeithFisher

October4,2016at1:29pm

justtoconfirmupdatingtheparameterto0inthexmlfilefixed
theissuethesereportswerehaving

SateeshKumar

October4,2016at2:13pm

canweknowwhatispathandnameoffile.
Thanks

KeithFisher

October4,2016at2:20pm

HiSateesh,
Roberthasalreadydescribedthefile
andthedirectoryabove(inthesection
immediatelyunderneaththegraphic
showingparallelversussequential
queries).
HoweverIhavesincefoundthat
a:thereisasecondcopyofthefileon
theserverunderwin64_x64aswellas
win32_x86
b:changingeitherxmlfilehasno
effectonqueriesrunninginthe
browserversionofWebitoaffect

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 22/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

thatyouneedtochangetheproperties
ofthewebiprocessingservers
themselves(change64to1,and
disableparallelprocessingfor
scheduling).
thanks
Keith

TedUeda

October4,2016at2:30pm

SoundslikeSAPNote
2345997thatsfixedwith
4.2SP04.Ifyourclient
hasaccesstoSAP
Support,theycanhavea
lookatthatNote.
Sincerely,
TedUeda

KeithFisher

October4,2016at2:37pm

yesitsexactlythat,
thanks!shameIdidntfind
thatnoteyesterdaywhen
Iwasonsitemysearch
termsobviouslynot
preciseenough!
thanks
Keith

Share & Follow

Privacy TermsofUse LegalDisclosure Copyright Trademark Sitemap Newsletter

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 23/24
11/30/2016 NewWebIfeatureinBI4.2ParallelQueriesSAPBlogs

https://blogs.sap.com/2016/01/22/newwebifeatureinbi42parallelqueries/# 24/24