RE: SQL run time changed after DB upgrade but execution plan did not change

From: John Hurley <hurleyjohnb@xxxxxxxxx>
To: "jonathan@xxxxxxxxxxxxxxxxxx" <jonathan@xxxxxxxxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>, Amir.Hameed@xxxxxxxxx
Date: Sat, 27 Apr 2013 14:59:05 -0700 (PDT)

Of course you can always use /*+ MONITOR */ hint from certain versions on ... ( 
depending on oracle licensing factors ) ... 

--
//www.freelists.org/webpage/oracle-l

References:
- RE: SQL run time changed after DB upgrade but execution plan did not change
  - From: Hameed, Amir

Other related posts:

» SQL run time changed after DB upgrade but execution plan did not change- Hameed, Amir
» RE: SQL run time changed after DB upgrade but execution plan did not change- Mark W. Farnham
» RE: SQL run time changed after DB upgrade but execution plan did not change- Jonathan Lewis
» RE: SQL run time changed after DB upgrade but execution plan did not change- Hameed, Amir
» RE: SQL run time changed after DB upgrade but execution plan did not change- Jonathan Lewis
» RE: SQL run time changed after DB upgrade but execution plan did not change- Hameed, Amir
» RE: SQL run time changed after DB upgrade but execution plan did not change - John Hurley
» RE: SQL run time changed after DB upgrade but execution plan did not change- Mark W. Farnham
» RE: SQL run time changed after DB upgrade but execution plan did not change- Hameed, Amir
» RE: SQL run time changed after DB upgrade but execution plan did not change- Mark W. Farnham
» RE: SQL run time changed after DB upgrade but execution plan did not change- Hameed, Amir
» Re: SQL run time changed after DB upgrade but execution plan did not change- Jonathan Lewis
» RE: SQL run time changed after DB upgrade but execution plan did not change- Hameed, Amir
» Re: SQL run time changed after DB upgrade but execution plan did not change- Jonathan Lewis