Re: Distributed Queries and 10046 Traces
- From: Mladen Gogala <gogala@xxxxxxxxxxxxx>
- To: ian@xxxxxxxxxxxxxxxxx
- Date: Sat, 12 Mar 2005 07:39:00 +0000
On 03/11/2005 01:09:18 PM, MacGregor, Ian A. wrote:
> The question about the remote join prompted this one. If one traces a =
=3D
> session which includes selecting a data over a database link, one can =3D
> use a logon/logoff triggers to trace the remote session. Where in =3D
> either trace is the time spent to ship the data over the link. On the =
=3D
> local side there are the "message from dblink" waits, but do they =3D
> include the time to ship the rows or just the time the remote database =
=3D
> took to respond? =3D20
>=20
> Ian MacGregor
> Stanford Linear Accelerator Center
> ian@xxxxxxxxxxxxxxxxx
> --
> //www.freelists.org/webpage/oracle-l
>=20
Ian, it includes any wait for any data from db link. If you want to trace =
Oracle*Net data,
you should really use event 10079, in addition to 10046.
10079, 00000, "trace data sent/received via SQL*Net"
// *Cause:
// *Action: level 1 - trace network ops to/from client
// level 2 - in addition to level 1, dump data
// level 4 - trace network ops to/from dblink
// level 8 - in addition to level 4, dump data
In your case, level 1 would probably be sufficient.
--=20
Mladen Gogala
Oracle DBA
--
//www.freelists.org/webpage/oracle-l
Other related posts:
