cancel
Showing results for 
Search instead for 
Did you mean: 

High response times in UCWB_INT06, Access on table UCST001

Former Member
0 Kudos

Hello all,
we are experiencing high (~ 277s) response times in transaction UCWB_INT06.

This is because there are repeated full table scans on table UCST001:

SELECT
*
FROM
"UCST001"
WHERE
"MANDT"=:A0 AND "ENDDATE"=:A1 AND "ENDTIME">=:A2 AND "ENDTIME"<:A3

Execution Plan
From: V$SQL_PLAN sql_id: 1y0nc22nd4tmz
SELECT STATEMENT PLAN_HASH_VALUE: 1608570456 Valid as of: Estimated Costs= 19.109 Estimated Rows= 0
Optimizer: ALL_ROWS Estim. CPU-Costs = 19.109 Estim. IO-Costs = 0
2 FILTER
2 Filter predicates: :A2<:A3
1 TABLE ACCESS FULL UCST001
1 Estimated Costs= 19.109 Estimated Rows= 2
1 Filter predicates:
1 ("ENDDATE"=:A1 AND "ENDTIME">=:A2 AND "ENDTIME"<:A3 AND "MANDT"=:A0)
1 Estim. Bytes: 2.976
1 Estim. CPU-Costs = 68 Estim. IO-Costs = 19.041

This SQL is responsible for approx. 50% of all DB physical read operations.

In our system no indexes exist on columns ENDDATE and ENDTIME. I assume, that these would tremendously speed up things but I don't want to mess with the SAP DB schema.

Any suggestions / comments on this?

Bes Regards,

Thorsten

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Throsten,

probably not an answer you were looking for, but i keep hearing that HANA has no indexes. also, SEM-BCS was one of the early applications to be certified on it. btw, wouldn't your basis team have any suggestions about those indexes in the underlying RDBMS?

rgds,

greg

Former Member
0 Kudos

Is it SELECT from  within another SELECT? You'd better be off ( or find the proper basis forum).