Re: How to translate bind_data from v$sqlarea_plan_hash (and other related views)?
- From: "Mark J. Bobak" <mark.bobak@xxxxxxxxxxxxxxx>
- To: sac@xxxxxxxxxxxxx
- Date: Mon, 01 May 2006 11:52:13 -0400
I've never tried to interpret that data.
However, you can do a 10046 trace.
If you do trace at level 1, you get basic trace. At level 4, you also
get bind data, at level 8 you get wait events, and at level 12 you get
both binds and waits.
alter session set events '1004 trace name context level n, context
forever';
Replace the 'n' in the previous line with 1,4,8, or 12, as described
above. You can also use the DBMS_SUPPORT package to turn trace on and
off. Describe DBMS_SUPPORT for more info.
Hope that helps,
-Mark
On Mon, 2006-05-01 at 10:46 -0500, Schultz, Charles wrote:
> The documentation is rather flimsy on this column. I learned a lot
> when I read that the description of "bind_data" is "Bind data". Well
> blow me down! =)
>
> Does anyone know how this RAW value is formatted? Or, if there is a
> better way to grab bind variables from the data dictionary, please let
> me know.
>
> Thanks much,
>
> charles schultz
> oracle dba
> aits - adsd
> university of illinois
>
>
--
http://www.freelists.org/webpage/oracle-l
- References:
- How to translate bind_data from v$sqlarea_plan_hash (and other related views)?
- From: Schultz, Charles
Other related posts:
- » How to translate bind_data from v$sqlarea_plan_hash (and other related views)?
- » Re: How to translate bind_data from v$sqlarea_plan_hash (and other related views)?
- How to translate bind_data from v$sqlarea_plan_hash (and other related views)?
- From: Schultz, Charles