Could you help me analyze information from "set autotrace on" when a query is executed? I mean, I know full table scans are heavy on big tables. But which order points should we look at to understand output and improve execution (e.g., consistent get statistics, costs at explain plans, full index scan steps, hash join steps?). Could you explain a little about output statistics?
You should try to reduce the amount of work done. Fewer consistent gets and fewer disk reads will improve performance. The best way to measure performance is to measure the amount of time a query takes to run. In SQL*Plus, issue a SET TIMING ON command, which will tell you the elapsed time for an operation. For more information, consult the Oracle Performance Tuning manual.
Dig Deeper on Oracle database performance problems and tuning
I am updating 80% of the rows in a 30-column (6 VC  and a blob) table. I have the STD 10% pctfree set up. I am getting fair throughput,...
We are starting to upgrade to Oracle 10g and support a PeopleSoft application on AIX5L. Which initialization parameters do you consider important for...
Can I install the Oracle 8i client and the Oracle 10g client on Windows XP?