Help understand raw trace data.

The procedure accepts  the following parameters:

   ALOGID NUMBER;
   AINTREF VARCHAR2(50);
   ACLIENTTYPE NUMBER;
   ACLIENTID VARCHAR2(20);
   ACLIENTSUBID VARCHAR2(50);
   ASTARTTIME varchar2(20);
   ACHANNEL NUMBER;
   AINITUSERGROUP NUMBER;
   AINITUSERGROUPNAME VARCHAR2(50);
   AINITUSERID VARCHAR2(100);
   AINITUSERNAME VARCHAR2(50);
   AREFERENCE VARCHAR2(50);
   ADATA VARCHAR2(500);
   AVERIFIED CHAR(1);
   ACLIENTCATEGORY NUMBER;
   ACLIENTNAME VARCHAR2(255);
   AENDDATE varchar2(20);
 

And it is being called via JDBC, but I have no access to the calling routine.
 

The main problem is that this query is used by a telephone based application and at times takes 2 seconds or more to respond but most of the time it has a subsecond response. However the database is being blamed but I do not think this is the case, I am looking at gathering evidence and the trace was my starting point.
 
 

Thanks
 

Fred

--
http://www.freelists.org/webpage/oracle-l