Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: managing open database links?

Re: managing open database links?

From: Mark C. Stock <mcstockX_at_Xenquery>
Date: Thu, 20 Apr 2006 16:00:56 -0400
Message-ID: <LdmdnT1-LPLmddrZnZ2dnUVZ_vadnZ2d@comcast.com>

<yong321_at_yahoo.com> wrote in message
news:1145556797.556896.221660_at_v46g2000cwv.googlegroups.com...
: Mark C. Stock wrote:
: >
: > but i think the following will probably do it for all incoming db link
: > connections:
: >
: > select *
: > from v$session
: > where upper(program) like 'ORACLE%'
: > and username is not null
: >
: > the assumption is that all sessions for incoming db links will be from
an
: > oracle executable of some sort -- 'ORACLE.EXE' or something like
: > 'oracle_at_somehostname (TNS V1-V3)'. so will the background processes, but
the
: > background processes do not have a username
: >
: > ++ mcs
:
: That's very smart! You could also say type = 'USER' in place of
: username is not null, and possibly put @ in the like string
: 'ORACLE%@%'.
:
: For outgoing sessions, how about checking for DX locks?
:
: select sid from v$lock where type = 'DX'
:
: You see this whenever there's a distributed transaction lock, including
: a distributed query. It goes away when the session rollbacks or
: commits.
:
: Yong Huang
:

i thought about the '@' but that does not show up for db link originating from windows (specific chase is Oracle XE)

i'll take another look at v$lock -- i didn't think i saw anything there before for a simple @dblink query

thanks.

++ mcs Received on Thu Apr 20 2006 - 15:00:56 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US