On Wed, Feb 01, 2006 at 08:43:42AM -0600, Smith, Ron wrote:
> It was the trace in the SQLNET.ORA. The trace file had gotten to be over 2G.
Congrats. It is really nice that this worked out so well.
Take a higher level look at the situation now that the house is
not burning down:
- ask yourself if the method you used to solve the problem is reliable
- create a changelog
- edit the changelog when you make changes
- include timestamps
- check the changelog as needed
- study Milsap, Holt
- see yourself in chapt 1. I know I saw myself.
- if you don't have time, do it anyway
- ok, ok, you don't have time. read the cliffsnotes:
http://www.oracle.com/technology/oramag/oracle/04-jan/o14tech_perf.html
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Feb 01 2006 - 10:08:29 CST
