Re: How to trace what is happening inside the stored procedure

  • From: Nuno Souto <dbvision@xxxxxxxxxxxx>
  • To: "Oracle L (E-mail)" <oracle-l@xxxxxxxxxxxxx>
  • Date: Mon, 07 Feb 2005 08:49:08 +1100

Tanel P=F5der apparently said,on my timestamp of 7/02/2005 12:07 AM:

> Could it be because Oracle doesn't want to grow the sessions fixed arra=
y too=20
> large?

What, from 32 bytes?  In this day and age of multi-Gb memories even in PC=
's?
Sounds to me as a very weird and myopic way of keeping memory low,
particularly when the per session memory for Oracle is already in the
multi-Mb arena...

> As one possdible workaround, you could write and use a wrapper for=20

Oh, I know the workaround.


--=20
Cheers
Nuno Souto
in sunny Sydney, Australia
dbvision@xxxxxxxxxxxx
--
//www.freelists.org/webpage/oracle-l

Other related posts: