| Analyze increases cost [message #192841] |
Wed, 13 September 2006 20:21  |
manish mendiratta
Messages: 110
Registered: May 2002
|
Senior Member |
|
|
Hi Guys, I have two questions.
I have this qry which runs very slow in Prod.
However, it runs pretty fine in TEST DB. It uses the same execution path as in TEST. Uses the same index(coluns indexed are same in TEST and PROD).Tables / Indexes are analyzed on PRod.
I am not able to understand what's making this qry very slow on PROD. Data in test are not that hugely different.
What should i do to makeit run faster.
Also, i analyzed the index on test to see if it makes a diff on execution but it increased the cost of qry after analyze.
Please suggest.
Thanks in advance.
Manish
|
|
|
|
| Re: Analyze increases cost [message #192849 is a reply to message #192841] |
Wed, 13 September 2006 21:31  |
rleishman
Messages: 3728
Registered: October 2005
Location: Melbourne, Australia
|
Senior Member |
|
|
Run both with SQL Trace and TK*Prof. Compare the TK*Prof results - they will show you either:
- Test is using a different plan to Prod
- Prod has different data to Test, resulting in more data read.
Instructions for SQL Trace and TKProf are in the Oracle Performance Tuning manual.
Ross Leishman
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
