Tarry,
Missed your post, could you please expand
Printable View
Tarry,
Missed your post, could you please expand
all full scans no wonder it takes long in the first execution, expected behaviour it´s not a parameter related problem
Pando,
It does full scans for the 2nd, 3rd...so why is the first one longer that the others?
Hi,
Because the db_cache holds any of the first selected blocks
so you would not have to read them again.
Orca
:cool:
There you go, while database is coming up, it's got a flushed SGA. Once you run your sql, it will fetch those blocks in the cache, and next time performance will be improved. Still 3 hours is a weird time. YOU didn't say anything on amount of data fetched !
This now affects any in-depth queries (such as joins
or subselects)
Does anyone else have areas that I might look at. I export the tables in the select statement to a test database and the script run fine.