Hello!!
I agree with Cliff. There is a debugging tool in UNIX called oradbx that
allows you to run dynamic tracing against a given OS-level process (which
translates to a SID on the database). Using this tool will allow you to
see where a given event is waiting (i.e. latch wait, db file scattered
read (full table scans), etc.).
If you don;t have that particular type of tool on your given platform,
alter your entry point form so that it does a pre-form trigger that fires
the statement:
alter session set sql_trace true;
This will alter your current session, when you exec your app, and turn
tracing on for your session. Run through the entire gambit, using as much
"real data" where possible. When you are finished, find the trace file
associated with the time you fiinished running the test and translate (for
lack of a better word) the file using tkprof. Find all the bad queries
and resolve them.
Good Luck and let us know how it goes!
Ernst W. Renner
Sr. DBA/Systems Architect
ITT Hartford Life Co. VISTA
erenner_at_itthartford.com
Received on Sun Nov 24 1996 - 00:00:00 CST
