Re: TEMP tablespace problem

What she was doing was breaking her client connection but not terminating the shadow process spawned on her behalf to complete the work request (two-task architecture and all that). Sounds like you need to turn on dead connection detection by specifying an EXPIRE_TIME value in your server-based sqlnet.ora file and educating your clients.

-Howie

RobW95 wrote:

> We have been experiencing some problems with our Temp tablespace. It is
> actually happening in two of our instances and it is basically the same
> problem. Everything is find for extended periods of time and then suddenly we
> notice that the temp tablespace is maxed out. It seems like they are big enough
> (100M in one, and 300M in the other). My guess is that the culprit is MS
> ACCESS, which our users utilize to query against the databases. One time when
> the 300M temp tablespace was maxed out I saw in V$session one woman who was
> running 10 Access queries at one time. She would submit one, it would run for
> about 15 minutes, she would get impatient when it didn't return results, and
> then just close Access. My guess is that this does not terminate Oracles
> response to the query request. She did this ten times and suddenly the temp
> tablespace is maxed out.
>
> Has anybody else experienced this problem? The only solution that we have found
> so far is to take the tablespace offline/online. Thanks. Rob
Received on Sat Jan 31 1998 - 00:00:00 CST