OBIEE Performance: Saw.odbc.statement.fetch Takes a Long Time And Affects Dashboard Performance (Doc ID 1509990.1)

Last updated on MARCH 23, 2015

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.5.0 [1308] and later
Information in this document applies to any platform.

Symptoms

Users notice a slow performance of many dashboards and are negatively affected due to this issue.

The Presentation Server log reports the saw.odbc.statement.execute and saw.odbc.statement.fetch often gets more than 30 seconds.

Example:

1:
[2012-11-28T13:09:11.000+01:00] [OBIPS] [WARNING:16] [] [saw.odbc.statement.execute.timings] [ecid: 06f059979b3876e0:7c7a5de6:13b0858df5a:-8000-00000000000931bb,0:1:82] [tid: 5528] SQLExecDirectW returned in 147454 msec(s).[[
File:odbcstatementimpl.cpp
Line:132
Location:
saw.odbc.statement.execute.timings
saw.odbc.statement.execute
saw.queryCache.odbcExecuter.execute
saw.querycache.executeQuery
saw.threadpool
saw.threads
ConnId: 100
StmtId: 5078
ecid: 06f059979b3876e0:7c7a5de6:13b0858df5a:-8000-00000000000931bb,0:1:82
ThreadID: 5528

********
2:
[2012-11-28T14:27:49.000+01:00] [OBIPS] [WARNING:16] [] [saw.odbc.statement.fetch] [ecid: 06f059979b3876e0:7c7a5de6:13b0858df5a:-8000-0000000000096736,0:1:189:7] [tid: 7340] SQLFetchScroll returned in 39937 msec(s).[[
File:odbcfields.cpp
Line:146
Location:
saw.odbc.statement.fetch
saw.hypercube.dxeApi
saw.querycache.executeQuery
saw.threadpool
saw.threads


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms