Performance - EBS (MOSC)

MOSC Banner

What are the typical reasons for a high lio when using a Index.

edited Nov 26, 2015 4:25AM in Performance - EBS (MOSC) 4 commentsAnswered ✓

What are the typical reasons for a high lio when using an Index.

I have 2 queries from same 11.2.0.4 tkprof output file. Unable to understand the reason for high lio by SQL1 below:

SQL1:

SELECT col1

FROM

table1 A WHERE col2 = :B2 AND col3 =:B1

call     count       cpu    elapsed       disk      query    current        rows

------- ------  -------- ---------- ---------- ---------- ----------  ----------

Parse        2      0.00       0.00          0          0          0           0

Execute  35148      0.89       0.88          0          0          0           0

Fetch    35148    136.34     139.29        340   28185241          0       35148

------- ------  -------- ---------- ---------- ---------- ----------  ----------

total    70298    137.24     140.18        340   28185241          0       35148

Misses in library cache during parse: 1

Misses in library cache during execute: 1

Optimizer mode: ALL_ROWS

Parsing user id: 85     (recursive depth: 1)

Number of plan statistics captured: 4

Rows (1st) Rows (avg) Rows (max)  Row Source Operation

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

EBS Performance Tags

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center