Database Tuning (MOSC)

MOSC Banner

SQL execution plan

Dear Experts,

We faced an issue last week end. All of the sudden, an execution plan was changed for a sql query. We created sql profile and after which a new plan was picked up. Below is the plan before and after creating sql profile.

OLD plan
=======
select unique(a.SEVA_DIP_FORM_ID) from SEVA_DIP_PILGRIM
b,SEVA_DIP_REGISTRATIONS a where  upper(b.PILIGRIM_ID_PROOF_NUMBER) =
:1  and (a.SEVA_DATE between :2  and :3  ) and a.SEVA_DIP_FORM_ID =
b.SEVA_DIP_FORM_ID and a.seva_dip_schedule_id = :4


Plan hash value: 3282040072


-----------------------------------------------------------------------------------------------------------------
| Id  | Operation                              | Name                   | Rows  | Bytes | Cost (%CPU)| Time     |
-----------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                       |                        |       |       |     9 (100)|   

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center