Oracle Execution Plan Bindings

Sometimes we query Gv$sql to see some running details for the same SQL different child cursors:

Selet T.inst_id,t.sql_id,t.child_number,t.plan_hash_value,t.last_active_time,t.elapsed_time/100000/decode ( t.executions,0,1,t.executions), t.elapsed_time/1000000,t.executions,t.sql_text from Gv$sql t where sql_id= ' xxx '

Through the above query if it involves the same SQL operation information is very different situation, basically go to the corresponding check, SQL is not a performance problem.

Some of the binding variables involved in SQL can be queried for gv$sql_bind_capture.

And the fixed problem of execution plan, this also according to the specific business scenario, for example the object data in the SQL is basically no change, especially like some historical analysis data.

Execution plan Fixed method: outline, SQL profile, SPM the difference between the three here I do not make a detailed statement. I'll do a demo for the SPM below.

Cond...

44017271

Oracle Execution Plan Bindings