Re: Do DB Links cause high execute and fetch stats?

g3000 wrote:
> Im on 9.2.0.4.0 AIX 64bit Enterprise Ed.
>
> I have a query that I traced. I ran tkprof on the trace file.
>
> It showed that there where alot of rows retreived and that executing
> the query took alot of time. The query ran for a little over an hour.
>
> Can I assume that the dblink causes the slow execute/fetch or is there
> something else I should check?
>
> The raw trace file has MANY statements like
>
> FETCH #1:c=0,e=346,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213288191
> FETCH #1:c=0,e=346,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213289848
> FETCH
> #1:c=10000,e=346,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213291506
> FETCH #1:c=0,e=346,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213293163
> FETCH #1:c=0,e=346,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213294625
> FETCH #1:c=0,e=345,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213296282
> FETCH #1:c=0,e=347,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213297941
> FETCH #1:c=0,e=603,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213455506
> FETCH #1:c=0,e=354,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213457163
> FETCH #1:c=0,e=347,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213458811
> FETCH #1:c=0,e=347,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213460468
> FETCH #1:c=0,e=347,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213462028
> FETCH #1:c=0,e=347,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213463686
> FETCH #1:c=0,e=348,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213465344
> FETCH
> #1:c=10000,e=386,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=963213466844

If it were due to the link, that would mean network waits. I'd expect to see wait events like ''SQL*Net more data from dblink' Received on Fri Aug 25 2006 - 14:30:20 CDT