Re: parallel query

In article <32638d03.2588120_at_n5.gbso.net>, <chuckh_at_dvol.com> writes:
> From: chuckh_at_dvol.com (Chuck Hamilton)
> Newsgroups: comp.databases.oracle
> Subject: Re: parallel query
> Date: Tue, 15 Oct 1996 13:14:33 GMT
> Organization: Do I look organized to you?
> Message-ID: <32638d03.2588120_at_n5.gbso.net>
> References: <325ca6a2.2452126_at_n5.gbso.net> <NEWTNews.845016912.3493.dafis_at_ppp.test.jccbi.gov> <32636daa.14657340_at_n5.gbso.net> <NEWTNews.845357109.26963.dafis_at_ppp.test.jccbi.gov>
> X-Newsreader: Forte Agent .99f/16.299
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> NNTP-Posting-Host: treasure_chest
> Lines: 26
> Path: news.ou.edu!news.ecn.uoknor.edu!munnari.OZ.AU!spool.mu.edu!howland.erols.net!newsfeed.internetmci.com!n5.gbso.net!
>
> Martin Douglas <dafis_at_ppp.test.jccbi.gov> wrote:
>
> >I have three processors on a DEC 2100 Alpha. And when I'm running parallel
> >query, I get multiple sessions for a users login. These are just the
> >processes that are started and are associated with the one user. In my Data
> >Warehouse, My users will sometimes reboot thier own system because of a bad
> >quiry. And then log back in. Conseqently, there are sometimes more sessions
> >going than just the number associated with the "Degree of Parallelism". You
> >should assume, (with OS striping), that your table is spread over all of the
> >drives that your tablespace is spread over. You should beable to identify
> >what datafiles are used by your tablespace. Ask your System Administrator
> >What drives these datafiles are striped on.
> >
> >Martin Douglas
> >
>
> Thanks for the info.
>
> BTW, is there an easy way to tell which session is the one the user
> actually connected as? When our users reboot because of a bad query,
> they call me and I kill their orphaned session with server manager.
> With all these extra sessions showing up with the same user name
> however, it's not easy to determine which is which. I usually go for
> the lowest SID# and start from there.
> --
> Chuck Hamilton
> chuckh_at_dvol.com
>
> This message delivered by electronic sled dogs. WOOF!
>
Well I will not be much help their, I just kill all pof the user's sessions. If you have a tool that can capture the SQL statement, you can usually determine which is the parent session. I use EXPLAIN, new version is Plan Analyizer. I can't remember who makes it now. but its a usefull tool. I'll try and respond tommorow with the maker.

Martin Douglas Received on Tue Oct 15 1996 - 00:00:00 CEST