TRACE file question

Question

I traced a user session against our TEST database to try and find out why an error is occuring. That trace file was quite large, with several queries showing up as going against SYSTEM tables:
select /*+ index(idl_sb4$ i_idl_sb41) +*/ piece#,length,piece
from
idl_sb4$ where obj#=:1 and part=:2 and version=:3 order by piece#When I traced a session against the PRODUCTION database there were far fewer entries. In fact, here were the differences:
TEST
       1  session in tracefile.
      13  user  SQL statements in trace file.
     109  internal SQL statements in trace file.
     122  SQL statements in trace file.
      51  unique SQL statements in trace file.
    3964  lines in trace file.
       0  elapsed seconds in trace file.PROD
       1  session in tracefile.
      15  user  SQL statements in trace file.
       3  internal SQL statements in trace file.
      18  SQL statements in trace file.
      17  unique SQL statements in trace file.
     650  lines in trace file.
       0  elapsed seconds in trace file.Why is there a difference between the two. The section of the Form throwing the error in TEST has not been changed from what's in PROD. But, I'm missing 2 user statements, one of which is the one I'm most interested in.
Thanks
-Chuck

Answer 1

Thank you very much, Mr. Forstmann, for your quick response.
It is really helpful. But I have one further question. Since our server space is limited and we can't keep those trace files forever. So I still need to delete inactive trace files to save some space. Could you please tell how to found out if files are open or closed in a SunOS 5.10 server?
Thanks a lot,
Shirley