| Problem with Analyze [message #57153] |
Thu, 22 May 2003 12:03  |
V Guru
Messages: 3
Registered: May 2002
|
Junior Member |
|
|
Hello,
I have a table 'X' which consists of 12000 rows. This table was altered as a new column was added. After the table was altered, the application accessing this table ran fine (17 minutes). When the appln. was run again after the analyze was done on the table, the appln takes about 60 m as opposed to 17m. What could be the problem?
Appreciate any responses.
Thanks,
VG
|
|
|
|
| Re: Problem with Analyze [message #57157 is a reply to message #57153] |
Fri, 23 May 2003 03:34  |
psmyth
Messages: 81
Registered: October 2002
|
Member |
|
|
You are being entertained by the Cost Based Optimizer ;-)
There is a lot of info on metalink and elsewhere about execution plans for sql and how they are affected by the CBO and the optimizer_mode and the level of 'analysis' that you have run. And when you've read it all, you'll find that Oracle themselves are a bit vague about the whole thing.
To get your issue sorted out, the most effective method will be to put 'hints' in the sql for the part of the application that accesses the table.
The reason being that having recent stats is always best, and given that, its simplest to tailor the parts that don't benefit from the CBO.
Have fun!
|
|
|
|
| Re: Problem with Analyze [message #57193 is a reply to message #57153] |
Tue, 27 May 2003 22:58 |
tejinder
Messages: 6
Registered: January 2002
|
Junior Member |
|
|
Pls check the optimizer_mode in init.ora parameter. See it is not RULE based.
Also see the explain plan of the qry and rebuild the indexes if required.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
